VCS comparison table

[Erik Bågfors]

On 10/25/06, John Arbash Meinel <john at arbash-meinel.com> wrote:
> Erik Bågfors wrote:
> > Sorry for going back to an old mail... but....
> >
> > On 10/24/06, Carl Worth <cworth at cworth.org> wrote:
> >> On Mon, 23 Oct 2006 19:26:57 -0500, "Matthew D. Fuller" wrote:
> >> >
> >> > On Mon, Oct 23, 2006 at 04:24:30PM -0700 I heard the voice of
> >> > Linus Torvalds, and lo! it spake thus:
> >> > >
> >> > > The problem? How do you show a commit that is _common_ to two
> >> > > branches, but has different revision names in them?
> >> >
> >> > Why would you?
> >>
>
> ...
>
> > Creates the picture you can see at
> > http://erik.bagfors.nu/bzr-plugins/dotrepo.png
> >
> > Please remember that this is a 15 min implementation and as such might
> > suck (the output is not perfect for example, it's slow, etc).  This
> > just brings in every revision in the entire repo, but to expand it to
> > just take the branches on the command line, is perfectly possible.
> >
> > But still.. there is no problem to create this.
> >
> > /Erik
>
>
> Erik, did you know about bzrtools' "graph-ancestry" command?
>
> It allows you to generate directly to .png (going through dot). And it
> colors the revisions, and you can use --merge-branch to indicate another
> branch, where it will color the common ancestors, and the merge point,
> and the revisions to be merged.

Really? Cool, I knew something like that existed, but not what it
could do or that it was in bzrtools.

The reason I did this was to get something that works on the
repository rather than on branches, but.. in general, this works much
better than the quick hack I did... :)

/Erik
-- 
google talk/jabber. zindar at gmail.com
SIP-phones: sip:erik_bagfors at gizmoproject.com
sip:17476714687 at proxy01.sipphone.com