A Guide to Branching in Mercurial

[Martin Geisler]

"Alexander Schatten" <ml_alexanderschatten at gmx.at> writes:

> thanks, I think I get the point.
>
> However, I wonder, if it would not be a good idea to add a feature
> here. I mean: I believe it is not a bad idea to keep also a crappy
> branch for documentation issues. But when I merge it (even dummy
> merge) it appears as if that this one was, in effect properly merged,
> when it actually was not.
>
> Would you not think, that it would be a good idea to add a feature
> that "names" such branches "dead end"; like "hg branch --dead-end
> [optional name]" then they would be seen in the tree view as branches
> (which they are), would not clutter the named branches, would not
> appear as regular merges, but as what they are: dead ends. In merge
> behaviour, they would behave like named branches though.
>
>
> Bad idea?

It's not a bad idea... Infact we do have a --close-branch argument for
the commit command. As far as I can tell, it operates on named branches.
A dead-end is for instance still present in 'hg heads'.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20090906/9653156c/attachment.pgp