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

Documentation: pack-refs --all vs default behaviour

Browse Source 
Document the recommended way to prime a repository with tons of
references with 'pack-refs --all -prune'.

Signed-off-by: Junio C Hamano <junkio@cox.net>
This commit is contained in:
Junio C Hamano 2007-01-25 22:51:49 -08:00
parent df373ea99a
commit af67e91c39
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -29,12 +29,23 @@ file and used if found.
Subsequent updates to branches always creates new file under Subsequent updates to branches always creates new file under
`$GIT_DIR/refs` hierarchy. `$GIT_DIR/refs` 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
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,
and next `pack-refs` (without `--all`) will leave them
unpacked.
OPTIONS OPTIONS
------- -------
\--all:: \--all::
The command by default packs all tags and leaves branch tips The command by default packs all tags and refs that are already
packed, and leaves other refs
alone. This is because branches are expected to be actively alone. This is because branches are expected to be actively
developed and packing their tips does not help performance. developed and packing their tips does not help performance.
This option causes branch tips to be packed as well. Useful for This option causes branch tips to be packed as well. Useful for