Back around July 10th this year, there were two emails, one an inquiry, the 
second a reply off the mark, about how to use the TortoiseHg GUI to create a 
new named branch.

The change log viewer does not show the branch name in the graphical display, 
though you can see it in the description window, and there is support for it in 
the custom filter, which is even helpful enough to have a drop-down with all 
the named branches' names in it.

If I've missed some option, please set me straight.
I cannot find any part of the TortoiseHg GUI where I can create a named branch. 
I thought the Commit window (either Internal or Qct, but unless I missed 
something, there was nothing there). I also have been unable to craft a search 
in the wiki or the bugtracker or the mailing list archive, that points me to an 
answer, so as a last resort, I'm posting here.

If not, unless this is an utterly trivial fix, I'm willing to wait until after 
0.4Final


--Doug

P.S. For those who care, I did an inquiry on the mercurial list about the 
overhead of using named branches for short-lived branches, but got no reply. I 
write a few scripts that created a repo with 1,000 named branches of 8 commits 
each. Neither hg log nor hg branches nor any other command that I thought to 
try, was slowed down... so "named branches live forever" is no reason to deny 
the TortoiseHg GUI the ability to create them, nor does having lots of them 
seem to make any difference to performance, though maybe I missed testing 
something.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss

Reply via email to