1GIT-PACK-REFS(1) Git Manual GIT-PACK-REFS(1)
2
6 git-pack-refs - Pack heads and tags for efficient repository access
7
9 git-pack-refs [--all] [--no-prune]
10
12 Traditionally, tips of branches and tags (collectively known as refs)
13 were stored one file per ref under $GIT_DIR/refs directory. While many
14 branch tips tend to be updated often, most tags and some branch tips
15 are never updated. When a repository has hundreds or thousands of tags,
16 this one-file-per-ref format both wastes storage and hurts performance.
17 This command is used to solve the storage and performance problem by
19 stashing the refs in a single file, $GIT_DIR/packed-refs. When a ref is
20 missing from the traditional $GIT_DIR/refs hierarchy, it is looked up
21 in this file and used if found.
22 Subsequent updates to branches always creates new file under
24 $GIT_DIR/refs hierarchy.
25 A recommended practice to deal with a repository with too many refs is
27 to pack its refs with --all --prune once, and occasionally run
28 git-pack-refs --prune. Tags are by definition stationary and are not
29 expected to change. Branch heads will be packed with the initial
30 pack-refs --all, but only the currently active branch heads will become
31 unpacked, and next pack-refs (without --all) will leave them unpacked.
32
34 --all
35 The command by default packs all tags and refs that are already
36 packed, and leaves other refs alone. This is because branches are
37 expected to be actively developed and packing their tips does not
38 help performance. This option causes branch tips to be packed as
39 well. Useful for a repository with many branches of historical
40 interests.
41 --no-prune
43 The command usually removes loose refs under $GIT_DIR/refs
44 hierarchy after packing them. This option tells it not to.
45
47 Written by Linus Torvalds <torvalds@osdl.org>
48
50 Part of the git(7) suite
51Git 1.5.3.3 10/09/2007 GIT-PACK-REFS(1)