changeset, multiple branch

Thomas Arendsen Hein thomas at intevation.de
Thu Jun 8 02:18:57 CDT 2006


* Aldrik KLEBER <aldrik.kleber at tiscali.fr> [20060608 01:04]:
> Someone can explain me how a changeset when I do a "hg log -b" can be part of 
> many branch, and not only one ?

Imagine this:

 |---0.9---1.0---stable---1.0.1---1.0.2---A
             \---devel---1.1.0---1.1.1---B

A would be on the stable branch, but also on 1.0.1 and 1.0.2
B would be on the devel branch, but also on 1.1.0 and 1.1.1

And probably both may list 1.0 and 0.9 as their branch.

On the other hand, the current implementation seems to be buggy, as
you can see with "hg tip -b" on the Mercurial repository:

changeset:   2406:4a678e408ce5
tag:         tip
branch:      0.8.1 0.9 0.8
user:        Vadim Gelfer <vadim.gelfer at gmail.com>
date:        Wed Jun 07 10:33:26 2006 -0700
summary:     revert: check for changes against target rev

Only 0.8, 0.8.1 and 0.9 get listed, but not the older tags.

We talked about this on the London sprint, but have not found a
solution yet how to handle this.

Until then I'd recommend using separate repositories for different
(named) branches.

Thomas

-- 
Email: thomas at intevation.de
http://intevation.de/~thomas/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.selenic.com/pipermail/mercurial/attachments/20060608/266552b5/attachment-0001.pgp


More information about the Mercurial mailing list