Branch and tag name conflict

[wbyoung at fadingred.com]

I'd agree that it's the user's problem/mistake, but it was a little
surprising suddenly I could no longer merge my branch into the default
branch.

I think it goes against Mercurial's philosophy of least surprise, and
would agree with you that printing a message, but still allowing the
name conflict to occur would solve the "problem" just fine.

Thanks for the feedback.


Whitney Young
FadingRed
wbyoung at fadingred.com
www.fadingred.com



On Fri, Apr 16, 2010 at 2:44 AM, Dirkjan Ochtman <dirkjan at ochtman.nl> wrote:
> On Fri, Apr 16, 2010 at 09:35, Sune Foldager <cryo at cyanite.org> wrote:
>> You may have a point there; I wonder if the current behavior is
>> intentional or just a result of features being added through many
>> iterations.
>
> From the last time this came up, I think we decided it was PEBKAC.
>
> IMO it would be nice to print a warning without aborting (like
> commit's 'created a new head').
>
> Cheers,
>
> Dirkjan
>