docs/git-clone: clarify use of --no-hardlinks option
Current text claims optimization, implying the use of hardlinks, when this option ratchets down the level of efficiency. This change explains the difference made by using this option, namely copying instead of hardlinking, and why it may be useful. Signed-off-by: Albert L. Lash, IV <alash3@bloomberg.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Albert L. Lash, IV committed
Feb 8, 2014 at 15:41 UTC
897e3e454062d2bb9d3c1e4068caf4971fd713ff
1 file changed
+4
-7
Documentation/git-clone.txt
+4
-7
@@ -55,15 +55,12 @@ repository is specified as a URL, then this flag is ignored (and we
55
never use the local optimizations). Specifying `--no-local` will
56
override the default when `/path/to/repo` is given, using the regular
57
Git transport instead.
58
-+
59
-To force copying instead of hardlinking (which may be desirable if you
60
-are trying to make a back-up of your repository), but still avoid the
61
-usual "Git aware" transport mechanism, `--no-hardlinks` can be used.
58
59
--no-hardlinks::
64
- Optimize the cloning process from a repository on a
65
- local filesystem by copying files under `.git/objects`
66
- directory.
60
+ Force the cloning process from a repository on a local
61
+ filesystem to copy the files under the `.git/objects`
62
+ directory instead of using hardlinks. This may be desirable
63
+ if you are trying to make a back-up of your repository.
64
65
--shared::
66
-s::