summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLibravatar Jonathon Mah <me@JonathonMah.com>2013-07-18 09:53:25 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-07-18 16:23:46 -0700
commit4a81bfa1d97ed5d1952f5b94dd7eeedddc21d457 (patch)
tree618a1b20047e1e5a2002f3cc372ee842ed3907a1
parentGit 1.8.3 (diff)
downloadtgif-4a81bfa1d97ed5d1952f5b94dd7eeedddc21d457.tar.xz
Documentation: remove --prune from pack-refs examples
The option has been the default for a while, and doesn't otherwise appear in the page. Signed-off-by: Jonathon Mah <me@JonathonMah.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-pack-refs.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-pack-refs.txt b/Documentation/git-pack-refs.txt
index f131677478..154081f2de 100644
--- a/Documentation/git-pack-refs.txt
+++ b/Documentation/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,