Miklos Vajna  committed 28678b4

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 <>
Signed-off-by: Junio C Hamano <>

  • Participants
  • Parent commits 3b839fd
  • Branches master

Comments (0)

Files changed (1)

File Documentation/git-clone.txt

 	.git/objects/info/alternates to share the objects
 	with the source repository.  The resulting repository
 	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>::
 	If the reference repository is on the local machine