Differences between revisions 1 and 39 (spanning 38 versions)
Revision 1 as of 2006-11-28 23:05:54
Size: 593
Editor: corecode
Comment:
Revision 39 as of 2013-08-30 16:57:27
Size: 347
Editor: TamaraLan
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Named branches allow assigning a symbolic name to not only one certain revision, like tags allow, but they provide a mechanism to assign a name to a complete branch.

To start working on a branch which is rooted at the current working dir revision, invoke hg with:
{{{
  hg branch branchname
}}}

From this moment on, all commits will get tagged with the supplied branch name.

To get a list of all available branches, use:
{{{
  hg branches
}}}

When merging two named branches, the merge changeset will reside on the branch of the working dir. The other branches head stays.
Lise is my make though I don't really like getting to be called like exactly who. Years ago we moved to Nebraska. The performance I've been taking up for years is really a people manager. http://thumbs.dreamstime.com/thumbimg_3031/30310094.jpg Playing football is what I do every week. Check out my site here: http://fcall.net/mulberry-careers/

Lise is my make though I don't really like getting to be called like exactly who. Years ago we moved to Nebraska. The performance I've been taking up for years is really a people manager. http://thumbs.dreamstime.com/thumbimg_3031/30310094.jpg Playing football is what I do every week. Check out my site here: http://fcall.net/mulberry-careers/

NamedBranches (last edited 2013-12-26 09:53:26 by Tovim)