Mercurial > hg-stable
changeset 6509:5279848424e7
issue 1053: heavily qualify the "cp -al" advice for cloning
| author | Bryan O'Sullivan <bos@serpentine.com> |
|---|---|
| date | Wed, 09 Apr 2008 16:02:37 -0700 |
| parents | 4b2c266bf059 |
| children | 37ab2331b94c |
| files | mercurial/commands.py |
| diffstat | 1 files changed, 8 insertions(+), 6 deletions(-) [+] |
line wrap: on
line diff
--- a/mercurial/commands.py Wed Apr 09 15:49:20 2008 -0700 +++ b/mercurial/commands.py Wed Apr 09 16:02:37 2008 -0700 @@ -506,15 +506,17 @@ do not report errors. In these cases, use the --pull option to avoid hardlinking. - You can safely clone repositories and checked out files using full - hardlinks with + In some cases, you can clone repositories and checked out files + using full hardlinks with $ cp -al REPO REPOCLONE - which is the fastest way to clone. However, 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). + 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. If you use the -r option to clone up to a specific revision, no subsequent revisions will be present in the cloned repository.