VCS comparison table
Erik Bågfors
zindar at gmail.com
Tue Oct 24 08:31:07 BST 2006
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?
>
> Assume you've got two long-lived branches and one periodically gets
> merged into the other one. The combined history might look as follows
> (more recent commits first):
>
> f g
> | |
> d e
> |\ /
> b c
> |/
> a
>
> The point is that it is extremely nice to be able to visualize things
> that way. Say I've got a "dev" branch that points at f and a "stable"
> branch that points at g. With this, a command like:
>
> gitk dev stable
>
> would result in a picture just like the above. Can a similar figure be
> made with bzr? Or only the following two separate pictures:
The above picture can easily be created with bzr if you have a
utility/plugin that does it. There is none that does it yet, but there
are no problems doing one.
Of course, in such a context revision numbers have no use. But see,
revision numbers is not mandatory in bzr, so that's not a problem.
I haven't really had a need for such a tool, but I do see where it can
be very useful to have.
> f g
> | |
> d e
> |\ |
> b c c
> |/ |
> a a
>
This is what you would get if you visualize the two separate branches,
and not the common repository.
/Erik
--
google talk/jabber. zindar at gmail.com
SIP-phones: sip:erik_bagfors at gizmoproject.com
sip:17476714687 at proxy01.sipphone.com
More information about the bazaar
mailing list