[PATCH 0 of 9] improvements for named branches

Paul Franz theandromedan at gmail.com
Mon Mar 3 09:52:44 CST 2008


Alexis S. L. Carvalho wrote:
> Hi
>
> This patch series implements two features for named branches:
>
> - multi-headed branches (patches 1-4)
>
> - branch closing (patches 5-9)
>
>
> Just like a repo can have multiple heads, a named branch can easily grow
> multiple heads (two users commit stuff in their private repos and then
> pull the other).  So I think it makes sense to keep track of all the
> heads of a named branch.
>
> UI-wise this means that commands that want a single revision (e.g. diff)
> will complain that the name is ambiguous; commands that take multiple
> revisions (pull, push, log) will use all of the heads.  The exception is
> update, which will still update to the tip of the branch (but I think
> I'll add a "warning: branch has multiple heads").  merge will also want
> some extra smarts to be more user-friendly.
>
>
>   

I am not sure how a branch can have multiple heads. Sorry, I am new to 
Mercurial so if I am missing something please tell me.  If Mercurial 
currently does not support it and you are asking to add support for it. 
I would say that it would be a bad idea just for sake of developers sanity.

BTW,  the idea of obsoleting/hiding a branch via closing it is a good idea.



More information about the Mercurial-devel mailing list