Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
git-clone -s: document problems with git gc --prune
author
Miklos Vajna
<vmiklos@frugalware.org>
Tue, 22 Jan 2008 22:12:25 +0000
(23:12 +0100)
committer
Junio C Hamano
<gitster@pobox.com>
Wed, 23 Jan 2008 18:09:54 +0000
(10:09 -0800)
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>
Documentation/git-clone.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
3b839fd
)
diff --git
a/Documentation/git-clone.txt
b/Documentation/git-clone.txt
index fdccbd4cbe8fcb336b412d75dc070a5d7b5acb1e..23418816146d0b65eeabdd7a3d67dcd7e8c760e1 100644
(file)
--- 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.
.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
--reference <repository>::
If the reference repository is on the local machine