On Fri, 2009-02-06 at 00:28 -0500, Douglas Philips wrote: > On or about 2009 Jan 22, at 6:56 PM, Steve Borho indited: > > It's funny, I just added 'branch support' to my TODO list. We need to > > figure out a way of allowing the user to specify a new branch name > > at commit time, and also allow the user to set the new --close-branch > > flag that will be in 1.2. Nothing obvious springs up at me. > > This is particularly interesting to me because my group at work uses > named branches regularly (not frequently, but regularly). And so > they've had to use the command line to set the branch name before > right-clicking into the commit dialog. > > Hence, it is possible that there is a pending branch name already set > when the commit dialog is started. > Since "all the existing branch names" are known (just as all tag names > are known), it would be handy to see them. Of course reusing a branch > name for a disjoint branch is frowned upon, and I suggest being able > to browse the existing branch names so that one can easily see what > one should avoid picking. > > As to the --close-branch, that seems to be a simple checkbox?
That seems somewhat obvious, but not where to put it where it doesn't occupy precious real-estate. It's a rarely used feature. > As to naming the branch of a commit-to-be, a text entry box such as is > used to enter new tag names would seem appropriate, as would some kind > of feedback indicating that the commit would create a new branch. The commit tool on crew has this text entry above the message entry box and just to the left of the message history drop-down box. It loads the text entry with the branch name of your working directory. If you modify the branch name, it will ask you to verify creating a new branch. If your name matches an existing branch, it will ask you if that's really what you wanted to do. I thought about making it a drop-down as you suggested, but then this might lead people to try and re-use the old names.. tough call. > As soon as I can get my hands on the latest experimental auto build > I'll look at the commit dialog and see if I can generate some more > concrete suggestions. Look forward to it. -- Steve ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
