mercurial/commands.py
changeset 2762 2df98f616645
parent 2761 0aa458261901
child 2763 0eb3a0d1c454
equal deleted inserted replaced
2761:0aa458261901 2762:2df98f616645
   995 
   995 
   996     The location of the source is added to the new repository's
   996     The location of the source is added to the new repository's
   997     .hg/hgrc file, as the default to be used for future pulls.
   997     .hg/hgrc file, as the default to be used for future pulls.
   998 
   998 
   999     For efficiency, hardlinks are used for cloning whenever the source
   999     For efficiency, hardlinks are used for cloning whenever the source
  1000     and destination are on the same filesystem.  Some filesystems,
  1000     and destination are on the same filesystem (note this applies only
  1001     such as AFS, implement hardlinking incorrectly, but do not report
  1001     to the repository data, not to the checked out files).  Some
  1002     errors.  In these cases, use the --pull option to avoid
  1002     filesystems, such as AFS, implement hardlinking incorrectly, but
  1003     hardlinking.
  1003     do not report errors.  In these cases, use the --pull option to
       
  1004     avoid hardlinking.
       
  1005 
       
  1006     You can safely clone repositories and checked out files using full
       
  1007     hardlinks with
       
  1008 
       
  1009       $ cp -al REPO REPOCLONE
       
  1010 
       
  1011     which is the fastest way to clone. However, the operation is not
       
  1012     atomic (making sure REPO is not modified during the operation is
       
  1013     up to you) and you have to make sure your editor breaks hardlinks
       
  1014     (Emacs and most Linux Kernel tools do so).
  1004 
  1015 
  1005     See pull for valid source format details.
  1016     See pull for valid source format details.
  1006 
  1017 
  1007     It is possible to specify an ssh:// URL as the destination, but no
  1018     It is possible to specify an ssh:// URL as the destination, but no
  1008     .hg/hgrc will be created on the remote side. Look at the help text
  1019     .hg/hgrc will be created on the remote side. Look at the help text
  2927          _('hg cat [OPTION]... FILE...')),
  2938          _('hg cat [OPTION]... FILE...')),
  2928     "^clone":
  2939     "^clone":
  2929         (clone,
  2940         (clone,
  2930          [('U', 'noupdate', None, _('do not update the new working directory')),
  2941          [('U', 'noupdate', None, _('do not update the new working directory')),
  2931           ('r', 'rev', [],
  2942           ('r', 'rev', [],
  2932            _('a changeset you would like to have after cloning')),
  2943            _('a changeset you would like to have after cloning (note this forces the usage of --pull)')),
  2933           ('', 'pull', None, _('use pull protocol to copy metadata')),
  2944           ('', 'pull', None, _('use pull protocol to copy metadata')),
  2934           ('', 'uncompressed', None,
  2945           ('', 'uncompressed', None,
  2935            _('use uncompressed transfer (fast over LAN)')),
  2946            _('use uncompressed transfer (fast over LAN)')),
  2936           ('e', 'ssh', '', _('specify ssh command to use')),
  2947           ('e', 'ssh', '', _('specify ssh command to use')),
  2937           ('', 'remotecmd', '',
  2948           ('', 'remotecmd', '',