summaryrefslogtreecommitdiffstats
path: root/git-pack-refs.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-07-24 20:24:57 -0700
committerJunio C Hamano <gitster@pobox.com>2013-07-24 20:24:57 -0700
commitd7fccbf9c67ab9111bc853a5fc90aa87d2d3f9c0 (patch)
treec35d99c84c5b6f4e4c14928f9465522b255bfa8c /git-pack-refs.txt
parent58f587aef6ee6b6b759fe8f4dd500f471eee1b88 (diff)
downloadgit-htmldocs-d7fccbf9c67ab9111bc853a5fc90aa87d2d3f9c0.tar.gz
Autogenerated HTML docs for v1.8.4-rc0
Diffstat (limited to 'git-pack-refs.txt')
-rw-r--r--git-pack-refs.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/git-pack-refs.txt b/git-pack-refs.txt
index f13167747..154081f2d 100644
--- a/git-pack-refs.txt
+++ b/git-pack-refs.txt
@@ -33,8 +33,8 @@ Subsequent updates to branches always create new files under
`$GIT_DIR/refs` directory hierarchy.
A recommended practice to deal with a repository with too many
-refs is to pack its refs with `--all --prune` once, and
-occasionally run `git pack-refs --prune`. Tags are by
+refs is to pack its refs with `--all` once, and
+occasionally run `git pack-refs`. Tags are by
definition stationary and are not expected to change. Branch
heads will be packed with the initial `pack-refs --all`, but
only the currently active branch heads will become unpacked,