Idea for revision graph

This is kind of a hare-brained idea I had...

I was just thinking that it would be really cool if the lines on the
revision graph could be made to represent the distance between two branches,
so by looking at the graph, one sees how diverged two branches are. So for
example, you've started a spike from the trunk to develop a feature in. You
know the best practise says "merge the updates in the trunk to my branch as
often as possible so you'll have less merging pain later". But how often is
often enough? Perhaps you have people on your team that commit small
changes often - perhaps you have people on your team that don't really get
that that's a good idea yet, and just commit whatever they've changed at the
end of the day, and you're not allowed violence in the office.

It would be nice if one could hit the revision graph, and see the divergence
of a branch for another graphically. So perhaps something like number of
differences from A to B and B to A would determine the distance. Perhaps
there could be two lines per branch; one that represents A to B, one that
represents B to A. Then the user knows when he's getting dangerously
diverged from the trunk and needs to sync from it.

Just some "wouldn't it be cool if" thoughts, really...

Regards

Pete

email protected and scanned by AdvascanTM - keeping email useful - www.advascan.com

<p>This e-mail and any attachment are confidential and contain proprietary information, some or all of which may be legally privileged. It is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient, please notify the author immediately by telephone or by replying to this e-mail, and then delete all copies of the
e-mail on your system. If you are not the intended recipient, you must not use, disclose, distribute, copy, print or rely on this e-mail.</p>
Received on Wed Nov 22 12:29:32 2006