Revenge of the pretty pictures

[John Arbash Meinel]

Aaron Bentley wrote:
> Hi all,
> 
> I've further bent dot to my will, such that
> 1. graph-ancestry takes a --merge-branch parameter, and will calculate a
>  graph showing how the merge base was selected
> 2. Nodes are always ordered by distance-from-root
> 3. When ancestry-collapsing is on, the number of skipped nodes is shown
> on each each arrow.
> 4. Instead of semi-random numbers, nodes are identified either by: a)
> their position in a branch history, or b) the last 5 characters in their id.
> 5. Defaulted the font to 11-point Helvetica
> 
> All this and more in http://panoramicfeedback.com/opensource/bzrtools
> 
> Enjoy,
> 
> Aaron

You don't really need the dXXXX for revisions in the main branch, as
they are always the same distance as their revno. Perhaps you could
structure things as:

last 5 chars
Committer
Distance to root

That would give you:

  41dd5
Martin Pool
  r1385

Instead of:

  r1385
Martin Pool
  d1385

It would be nicer to have some other information to put there, but since
there isn't much that is small enough and worthy enough. Perhaps the
date of commit 2005-05-05 is pretty small, and might mean something.

Also, I think I like the clustered form more than the non-clustered. As
I think it makes the ancestry follow a nice line, and is a little bit
easier to follow. You might consider adding a "--no-cluster" in case
someone is scripting and the default changes in the future.

And finally, it would be nice to have a color code (possibly in --help),
so that we can figure out what --merge-branch means.

John
=:->
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050922/68c07d3d/attachment.pgp