Skip to content

Commit 897e3e4

Browse files
alash3gitster
authored andcommitted
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 <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent a2f6958 commit 897e3e4

File tree

1 file changed

+4
-7
lines changed

1 file changed

+4
-7
lines changed

Documentation/git-clone.txt

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -55,15 +55,12 @@ repository is specified as a URL, then this flag is ignored (and we
5555
never use the local optimizations). Specifying `--no-local` will
5656
override the default when `/path/to/repo` is given, using the regular
5757
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.
6258

6359
--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.
6764

6865
--shared::
6966
-s::

0 commit comments

Comments
 (0)