aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/git-clone.txt
diff options
context:
space:
mode:
authorMiklos Vajna <vmiklos@frugalware.org>2008-01-22 23:12:25 +0100
committerJunio C Hamano <gitster@pobox.com>2008-01-23 10:09:54 -0800
commit28678b4f2f2e449986de4a6fc2dc93b32299ca74 (patch)
tree0f22b02589485a89687d888bf03c2601195b48e1 /Documentation/git-clone.txt
parent3b839fd8610b440f072d0c1c0ec00801347f3793 (diff)
downloadgit-28678b4f2f2e449986de4a6fc2dc93b32299ca74.tar.gz
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>
Diffstat (limited to 'Documentation/git-clone.txt')
-rw-r--r--Documentation/git-clone.txt8
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index fdccbd4cbe..2341881614 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -62,6 +62,14 @@ OPTIONS
.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