Skip to content

Commit

Permalink
Documentation: remove --prune from pack-refs examples
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
Jonathon Mah authored and Junio C Hamano committed Jul 18, 2013
1 parent edca415 commit 4a81bfa
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Documentation/git-pack-refs.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Expand Down

0 comments on commit 4a81bfa

Please sign in to comment.