Skip to content

Commit 677f32c

Browse files
committed
Merge branch 'jm/doc-ref-prune'
* jm/doc-ref-prune: Documentation: fix git-prune example usage Documentation: remove --prune from pack-refs examples
2 parents dfb78f0 + 8c3ca72 commit 677f32c

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

Documentation/git-pack-refs.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,8 +33,8 @@ Subsequent updates to branches always create new files under
3333
`$GIT_DIR/refs` directory hierarchy.
3434

3535
A recommended practice to deal with a repository with too many
36-
refs is to pack its refs with `--all --prune` once, and
37-
occasionally run `git pack-refs --prune`. Tags are by
36+
refs is to pack its refs with `--all` once, and
37+
occasionally run `git pack-refs`. Tags are by
3838
definition stationary and are not expected to change. Branch
3939
heads will be packed with the initial `pack-refs --all`, but
4040
only the currently active branch heads will become unpacked,

Documentation/git-prune.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ borrows from your repository via its
5959
`.git/objects/info/alternates`:
6060

6161
------------
62-
$ git prune $(cd ../another && $(git rev-parse --all))
62+
$ git prune $(cd ../another && git rev-parse --all)
6363
------------
6464

6565
Notes

0 commit comments

Comments
 (0)