Mercurial Workflow: Feature seperation via named branches

Judson Wilson judson at
Tue Jun 14 11:47:09 CDT 2011

> The reason that note is there is that the #1 question we get about named
> branches by a wide margin is:
> "I made a temporary branch, how do I get rid of it?"
> The permanence of named branches is NOT an implementation detail, it's
> bedrock design. Thus, telling people not to create them willy-nilly is
> solid advice.

Curious if there is a more lightweight way to do this. Perhaps some kind 
of layer on top of a repo that could allow you to put min-branches on 
top, and then we could just deprecate the older model (or save it for 
real divergences in the trunk, such as a fork between a new major-version).

I personally would like to name feature branches in a visible manner 
when looking through the tree, but not to show up on a list of "mainline 
branches".  I know this can be accomplished using commit messages, but 
that can be cumbersome.

More information about the Mercurial mailing list