[PATCH 0 of 2 ] an optional format flag to force --pull on clone

Matt Mackall mpm at selenic.com
Fri Dec 9 18:28:41 UTC 2011


On Fri, 2011-12-09 at 15:57 -0200, Wagner Bruna wrote:
> This adds an optional 'pullonclone' format flag to force
> --pull usage when cloning from the repository. It is intended
> as a workaround for filesystems with poor hardlink support.

So does this mean there are hardlink issues still out there? If so, why
haven't we heard about them? And why would papering over them like this
be the right answer?

Or is it meant to disable pre-1.7.1 clients (the last revision I'm aware
of that had such issues)? If so, it hits way too wide a mark by
disabling 1.7 through 2.0. Simply upgrading to the dotencode format will
disable direct pulls by all clients before 1.7, leaving only 1.7 itself
vulnerable, if you happen to be at risk for:

 http://mercurial.selenic.com/bts/issue1866

And --pull is really not the right answer: it significantly slower than
plain old copy.

-- 
Mathematics is the supreme nostalgia of our time.





More information about the Mercurial-devel mailing list