This is an archive of the discontinued Mercurial Phabricator instance.

Differential D863

commands: remove suggestion to clone via `cp -al`
ClosedPublic

Authored by indygreg on Oct 1 2017, 6:31 AM.

Details

Reviewers
simpkins
durin42
Group Reviewers
hg-reviewers
Commits
rHGaea6344e989b: commands: remove suggestion to clone via `cp -al`
Summary

This was added in 2df98f616645 in 2006. This may be possible but it
seems like a bad idea to even suggest it.

Diff Detail

Repository
rHG Mercurial
Lint
Lint Skipped
Unit
Unit Tests Skipped

Event Timeline

indygreg created this revision.Oct 1 2017, 6:31 AM
simpkins accepted this revision.Oct 1 2017, 6:42 AM
simpkins added a subscriber: simpkins.

killitwithfire

durin42 accepted this revision.Oct 1 2017, 6:48 AM
This revision is now accepted and ready to land.Oct 1 2017, 6:48 AM
Closed by commit rHGaea6344e989b: commands: remove suggestion to clone via `cp -al` (authored by indygreg). · Explain WhyOct 1 2017, 6:55 AM
This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

PathPackages
Mmercurial/commands.py (12 lines)

Diff 2227

mercurial/commands.py

For efficiency, hardlinks are used for cloning whenever the For efficiency, hardlinks are used for cloning whenever the
source and destination are on the same filesystem (note this source and destination are on the same filesystem (note this
applies only to the repository data, not to the working applies only to the repository data, not to the working
directory). Some filesystems, such as AFS, implement hardlinking directory). Some filesystems, such as AFS, implement hardlinking
incorrectly, but do not report errors. In these cases, use the incorrectly, but do not report errors. In these cases, use the
--pull option to avoid hardlinking. --pull option to avoid hardlinking.
In some cases, you can clone repositories and the working
directory using full hardlinks with ::
$ cp -al REPO REPOCLONE
This is the fastest way to clone, but it is not always safe. The
operation is not atomic (making sure REPO is not modified during
the operation is up to you) and you have to make sure your
editor breaks hardlinks (Emacs and most Linux Kernel tools do
so). Also, this is not compatible with certain extensions that
place their metadata under the .hg directory, such as mq.
Mercurial will update the working directory to the first applicable Mercurial will update the working directory to the first applicable
revision from this list: revision from this list:
a) null if -U or the source repository has no changesets a) null if -U or the source repository has no changesets
b) if -u . and the source repository is local, the first parent of b) if -u . and the source repository is local, the first parent of
the source repository's working directory the source repository's working directory
c) the changeset specified with -u (if a branch name, this means the c) the changeset specified with -u (if a branch name, this means the
latest head of that branch) latest head of that branch)