Closed branch push behavior?

[Martin Geisler]

Matt Mackall <mpm at selenic.com> writes:

> On Tue, 2011-12-06 at 22:59 +0100, Martin Geisler wrote:

The rest was not so important, it was just a comment on the current
policy for pushing branches. I think the idea below is more interesting:

>> Here's a quick idea: could we let
>>
>>   hg branch --rename default
>>
>> add a changeset that
>>
>> 1) closes the current branch
>>
>> 2) makes "default" the current branch
>>
>> 3) says "please treat the ancestor changesets as if they were on the
>>    default branch" too
>
> Yuck.

Okay... I'll take that as a "no" then.

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://mercurial.aragost.com/kick-start/