Differences between revisions 1 and 47 (spanning 46 versions)
Revision 1 as of 2006-11-28 23:05:54
Size: 593
Editor: corecode
Comment:
Revision 47 as of 2013-08-31 12:19:07
Size: 295
Editor: VelvaGood
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.
I'm Robt. It's not a common task but what I like doing is performing football but I do not have the time lately. Administering databases is the best day job correct now. For years I've lately been living in Minnesota. Check out my website here: http://www.bagsoutletinmk.com/michaelkorsoutlet/

I'm Robt. It's not a common task but what I like doing is performing football but I do not have the time lately. Administering databases is the best day job correct now. For years I've lately been living in Minnesota. Check out my website here: http://www.bagsoutletinmk.com/michaelkorsoutlet/

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