On Fri, Jan 23, 2009 at 12:56 AM, Steve Borho <[email protected]> wrote:
> On Thu, Jan 22, 2009 at 5:40 PM, TK Soh <[email protected]> wrote:
>>
>> On Thu, Jan 22, 2009 at 4:08 PM, Peter Arrenbrecht
>> <[email protected]> wrote:
>> > I just went ahead and gave you push rights to
>> >
>> >  http://bitbucket.org/parren/thg-hg-crew-tip/overview/
>> >
>> > -parren
>>
>> Speaking of your repo, actually the 'hg-crew-tip' branch created in
>> your repo has been bugging me a little. Admittedly, I don't know much
>> about branches, and I personally have not come to appreciate the
>> importance of them in our model (obviously I'm very much a plain
>> one-clone-per-development kind of person ;-). So for now, I wonder if
>> you'd mind removing the branch from your repo somehow.
>
> 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.

If we had a branch list, then this might be a natural place for it.
Also for updating to a specific branch.

-parren

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Tortoisehg-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop

Reply via email to