[PATCH 2 of 4] clone to master bookmark if available

[Arne Babenhauserheide]

Am Donnerstag, 10. November 2011, 09:44:02 schrieb Victor Suba:
> The gittish way is that the bookmark's pulled from the remote aren't merged
> into your local
> namespace - they're tied to the alias of the remote, and they're treated as
> foreign heads that
> are ignored in push/pull commands.

That’s one of the things I don’t like about git, so it’s not something I would 
want replicated in Mercurial. 

In Mercurial you normally synchronize everything, so there’s no danger of 
accidently forgetting to push something important. If you want to only 
synchronize a part, you say so via hg pull -r <rev>. In that case all revs not 
needed for that rev are ignored. 

Mercurial is not git, and I don’t want it to be git, because I consider the 
behavior of Mercurial as far more useful than the one of git. 

Mercurial says “this is the project, if you don’t want to share, say so”

Git says “this is our repo, ask for what you want”

In that respect git is actually not truly distributed, because if you forgot 
to pull an important branch before going offline, you’re out of luck. If you 
don’t explicitely request everything, you rely on a central server.

In Mercurial that problem is far less likely, because it is not the default 
workflow. 

In short: Mercurial is no git. And I like that. 

Best wishes, 
Arne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 316 bytes
Desc: This is a digitally signed message part.
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20111110/77695072/attachment.pgp>