Browse Source

git-clone -s: document problems with git gc --prune

There is a scenario when using git clone -s and git gc --prune togother is
dangerous. Document this.

Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
maint
Miklos Vajna 17 years ago committed by Junio C Hamano
parent
commit
28678b4f2f
  1. 8
      Documentation/git-clone.txt

8
Documentation/git-clone.txt

@ -62,6 +62,14 @@ OPTIONS
.git/objects/info/alternates to share the objects .git/objects/info/alternates to share the objects
with the source repository. The resulting repository with the source repository. The resulting repository
starts out without any object of its own. starts out without any object of its own.
*NOTE*: this is a possibly dangerous operation; do *not* use
it unless you understand what it does. If you clone your
repository using this option, then delete branches in the
source repository and then run linkgit:git-gc[1] using the
'--prune' option in the source repository, it may remove
objects which are referenced by the cloned repository.




--reference <repository>:: --reference <repository>::
If the reference repository is on the local machine If the reference repository is on the local machine

Loading…
Cancel
Save