Using named branches (`hg branch`) for feature branches isn't recommended.

[Peter]

Arne Babenhauserheide-2 wrote:
> 
> / 
>> For true branching feature parity (named branches 
>> which don’t persist and don’t pollute). Mercurial would 
>> just need a way to state: 
> 
> 
>>    Don’t use this bookmark as head / a bookmark is never the tip
>>    (exept if it’s the only head of the default branch)
> 
> 
>> An alternative would be 
> 
>>   If a default/tip bookmark is available, always update to that.
> 
> 
>> with that, multiple bookmarked seads would make sense to me.  
>> Without it, they just add points of failure (because the default 
>> revision a clone starts with is not guaranteed to be an agreed 
>> upon stable revision: You could just stumble into an incomplete feature
>> branch).
> /
> 
> I like that idea (and especially the latter alternative for its
> implementation).  It would allow to have the advantages of named branches
> without having the maintenance, name conflict and performance issues of
> named branches. Just set a bookmark with a special name reserved by Hg
> (e.g. 'default') and hg update without an explicitly given changeset or
> bookmark does always update to that bookmark. As far as I understood Peter
> that's what he is looking for.   
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
> 


--
View this message in context: http://mercurial.808500.n3.nabble.com/Using-named-branches-hg-branch-for-feature-branches-isn-t-recommended-tp3141864p3166538.html
Sent from the General mailing list archive at Nabble.com.