summaryrefslogtreecommitdiffstats
path: root/git-clone.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2008-04-23 16:09:20 +0000
committerJunio C Hamano <junio@hera.kernel.org>2008-04-23 16:09:20 +0000
commita9aee78a156ad6299451294a61aebe2a73945d3c (patch)
tree67691d6e64c1ddd0806872a934a327873e57f53f /git-clone.txt
parent6a45be9321b1ee81baf74de51671f224407e5ad1 (diff)
downloadgit-htmldocs-a9aee78a156ad6299451294a61aebe2a73945d3c.tar.gz
Autogenerated HTML docs for v1.5.5.1-79-g57cf
Diffstat (limited to 'git-clone.txt')
-rw-r--r--git-clone.txt13
1 files changed, 9 insertions, 4 deletions
diff --git a/git-clone.txt b/git-clone.txt
index 975824301..9b564420c 100644
--- a/git-clone.txt
+++ b/git-clone.txt
@@ -65,10 +65,13 @@ OPTIONS
+
*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.
+repository using this option and then delete branches (or use any
+other git command that makes any existing commit unreferenced) in the
+source repository, some objects may become unreferenced (or dangling).
+These objects may be removed by normal git operations (such as git-commit[1])
+which automatically call git-gc[1]. If these objects are removed and
+were referenced by the cloned repository, then the cloned repository
+will become corrupt.
@@ -79,6 +82,8 @@ objects which are referenced by the cloned repository.
an already existing repository as an alternate will
require fewer objects to be copied from the repository
being cloned, reducing network and local storage costs.
++
+*NOTE*: see NOTE to --shared option.
--quiet::
-q::