Why you don't want to allow disabling "branches are global and permanent, did you want a bookmark"?

Adrian Buehlmann adrian at cadifra.com
Mon Aug 13 04:24:04 CDT 2012


On 2012-08-13 10:42, Arne Babenhauserheide wrote:
> Am Donnerstag, 9. August 2012, 22:48:52 schrieb Adrian Buehlmann:
>> What's more, your "shoot in the foot" argument is a complete red
>> herring. If you start using a tool that's supposed to store your data
>> but you refuse to read anything before using it, then you have clearly
>> done something wrong. Blame yourself.
> 
> So that’s what I should tell a git user who wants to contribute to my project?

Yes. At some point they have to accept the fact that the term "branch"
has a different definition from what it has on git. It's not the job of
the UI texts of Mercurial to be tailored for git refugees who refuse to
read help texts before applying commands.

Assuming that a git user can blindly start using Mercurial without
learning the concepts, and by assuming everything will work the same as
in git, or Mercurial will warn, is a false attitude IMHO. That won't work.

[FWIW, you seem to contradict with yourself (judging from your other
emails).]

> That’s exactly the attitude from git: “your fault, RTFM”.

How is that relevant here?

> Mercurial always was different, and that’s great! Let’s keep it the vcs which 
> just works - and helps you out, when you’re in a bind.

And what should we conclude from that?


More information about the Mercurial-devel mailing list