summaryrefslogtreecommitdiffstats
path: root/git-clone.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2020-09-25 15:50:12 -0700
committerJunio C Hamano <gitster@pobox.com>2020-09-25 15:50:12 -0700
commitc562f6d6447ae8aaa1066a8f3872de759638a6bc (patch)
tree9c3f0b788be8b8046c48ad4ffd901935941a9164 /git-clone.txt
parentb89e21bf03b9675dec757d6e63db8d859b034303 (diff)
downloadgit-htmldocs-c562f6d6447ae8aaa1066a8f3872de759638a6bc.tar.gz
Autogenerated HTML docs for v2.28.0-618-g9bc23
Diffstat (limited to 'git-clone.txt')
-rw-r--r--git-clone.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/git-clone.txt b/git-clone.txt
index c89831009..097e6a86c 100644
--- a/git-clone.txt
+++ b/git-clone.txt
@@ -78,9 +78,9 @@ 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`)
-which automatically call `git gc --auto`. (See linkgit:git-gc[1].)
-If these objects are removed and were referenced by the cloned repository,
-then the cloned repository will become corrupt.
+which automatically call `git maintenance run --auto`. (See
+linkgit:git-maintenance[1].) If these objects are removed and were referenced
+by the cloned repository, then the cloned repository will become corrupt.
+
Note that running `git repack` without the `--local` option in a repository
cloned with `--shared` will copy objects from the source repository into a pack