undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation: remove --prune from pack-refs examples

Browse Source 
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>
This commit is contained in:
Jonathon Mah 2013-07-18 09:53:25 -07:00 committed by Junio C Hamano
parent edca415256
commit 4a81bfa1d9
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/git-pack-refs.txt
View File

@ -33,8 +33,8 @@ Subsequent updates to branches always create new files under
`$GIT_DIR/refs` directory hierarchy. `$GIT_DIR/refs` directory hierarchy.
A recommended practice to deal with a repository with too many A recommended practice to deal with a repository with too many
refs is to pack its refs with `--all --prune` once, and refs is to pack its refs with `--all` once, and
occasionally run `git pack-refs --prune`. Tags are by occasionally run `git pack-refs`. Tags are by
definition stationary and are not expected to change. Branch definition stationary and are not expected to change. Branch
heads will be packed with the initial `pack-refs --all`, but heads will be packed with the initial `pack-refs --all`, but
only the currently active branch heads will become unpacked, only the currently active branch heads will become unpacked,