From 28678b4f2f2e449986de4a6fc2dc93b32299ca74 Mon Sep 17 00:00:00 2001 From: Miklos Vajna Date: Tue, 22 Jan 2008 23:12:25 +0100 Subject: 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 --- Documentation/git-clone.txt | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'Documentation/git-clone.txt') 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 :: If the reference repository is on the local machine -- cgit v1.2.3