clone fails if target is locked [and a bit on I/O ordering rules]

[Thomas Arendsen Hein]

* Bryan O'Sullivan <bos at serpentine.com> [20050816 17:13]:
> The fix is not to read-lock the cloned repository, but to have the
> hardlink code honour the ordering rules.

In the following discussion Matt came to the conclusion that a lock
is still necessary, because otherwise there may be file revisions in
the .hg/data directory not pointed to by a manifest.

While this is not directly a problem for Mercurial, 'hg verify' will
complain about this, because this may be a hint that something else
went wrong. To not spoil the usefulness of this, cloning by
hardlinking should obey and set a lock on the cloned and on the
target repository.

Thomas

-- 
Email: thomas at intevation.de
http://intevation.de/~thomas/