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

Merge branch 'jm/doc-ref-prune'

Browse Source 
* jm/doc-ref-prune:
  Documentation: fix git-prune example usage
  Documentation: remove --prune from pack-refs examples
This commit is contained in:
Junio C Hamano 2013-07-24 19:21:15 -07:00
commit 677f32c79f
2 changed files with 3 additions and 3 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,

2
Documentation/git-prune.txt
View File

@ -59,7 +59,7 @@ borrows from your repository via its
`.git/objects/info/alternates`: `.git/objects/info/alternates`:
------------ ------------
$ git prune $(cd ../another && $(git rev-parse --all)) $ git prune $(cd ../another && git rev-parse --all)
------------ ------------
Notes Notes