Mercurial > hg
changeset 2762:2df98f616645
Expand clone help with hardlink information
| author | Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com> |
|---|---|
| date | Tue, 01 Aug 2006 09:50:30 -0700 |
| parents | 0aa458261901 |
| children | 0eb3a0d1c454 |
| files | mercurial/commands.py |
| diffstat | 1 files changed, 16 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/mercurial/commands.py Wed Aug 02 03:17:06 2006 +0200 +++ b/mercurial/commands.py Tue Aug 01 09:50:30 2006 -0700 @@ -997,10 +997,21 @@ .hg/hgrc file, as the default to be used for future pulls. For efficiency, hardlinks are used for cloning whenever the source - and destination are on the same filesystem. Some filesystems, - such as AFS, implement hardlinking incorrectly, but do not report - errors. In these cases, use the --pull option to avoid - hardlinking. + and destination are on the same filesystem (note this applies only + to the repository data, not to the checked out files). Some + filesystems, such as AFS, implement hardlinking incorrectly, but + 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 + + $ 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). See pull for valid source format details. @@ -2929,7 +2940,7 @@ (clone, [('U', 'noupdate', None, _('do not update the new working directory')), ('r', 'rev', [], - _('a changeset you would like to have after cloning')), + _('a changeset you would like to have after cloning (note this forces the usage of --pull)')), ('', 'pull', None, _('use pull protocol to copy metadata')), ('', 'uncompressed', None, _('use uncompressed transfer (fast over LAN)')),