views:

1313

answers:

2

I downloaded TortoiseHg 1.0 for evaluation. For the life of me I can't figure out how to make a branch. It seems to understand branches (e.g. in its repository browser) but I just can't seem to find a way to make a branch. This seems like such a fundamental capability since out of the often touted benefits of DVC is the lightweight branching.

I Googled around and couldn't find much discussion of this topic (at least for recent versions) so I have to assume I'm missing something, right?

Update: So I flagged Chad Birch's answer below to answer the "new branch" issue. As he correctly points out, you do a commit and then click on the branch button to bring up the branch maintenance dialog which is where you create new branches. I kind of wish they had given us a context menu option for this. Once you've branched, the next natural question is how to merge and this is also not obvious. It turns out that option is buried in the repository explorer. You need to select the head of another branch, right-click and then select "Merge with...".

+12  A: 

As shown in the docs, all you should need to do is just click on the branch: default button near the top of the commit dialog, and change to a new branch name.

Chad Birch
Ah, I see where it says "pressing this button opens up a branch maintenance dialog". That does indeed open a dialog that, as it turns out, allows branches to be created but I do take issue with the statement "As shown in the docs" since there is no explicit mention of how to create a branch anywhere on that page that I could find.I wonder what branching did to deserve getting second class treatment in TortoiseHg (vs. the other Tortoise* tools where it is a first class context menu option). :-)
Michael Tiller
Oh, I wasn't trying to be insulting in a "RTFM" manner or anything like that, I just needed some sort of phrase to link to the relevant page with. Maybe "as vaguely implied in the docs" would have been more appropriate in this situation.
Chad Birch
No sweat. I wasn't trying to be insulting either. I just wanted to make it clear to anybody who came along to look at that link that you've really got to read between the lines in the docs to get the answer since it isn't explicitly mentioned.
Michael Tiller
+2  A: 

Most of the time in mercurial, you clone the repository to make a branch.

You can then merge the separate repositories once you made your edits and commits.

This might sound like it would take up a lot of disk space but on most operating systems, mercurial will make hardlinks instead of copying the files. Anyway, disk space is normally cheap, and because it's local it's rather fast.

If you think about it, every "checkout" (in svn terminology) or "clone" (in mercurial terminology) is really a branch that will probably be merged back so it makes lots of sense that clones are the common way of making branches.

blokeley