1GIT-REPACK(1) Git Manual GIT-REPACK(1)
2
6 git-repack - Pack unpacked objects in a repository
7
9 git repack [-a] [-A] [-d] [-f] [-F] [-l] [-n] [-q] [-b] [--window=<n>] [--depth=<n>] [--threads=<n>] [--keep-pack=<pack-name>]
10
12 This command is used to combine all objects that do not currently
13 reside in a "pack", into a pack. It can also be used to re-organize
14 existing packs into a single, more efficient pack.
15 A pack is a collection of objects, individually compressed, with delta
17 compression applied, stored in a single file, with an associated index
18 file.
19 Packs are used to reduce the load on mirror systems, backup engines,
21 disk storage, etc.
22
24 -a
25 Instead of incrementally packing the unpacked objects, pack
26 everything referenced into a single pack. Especially useful when
27 packing a repository that is used for private development. Use with
28 -d. This will clean up the objects that git prune leaves behind,
29 but git fsck --full --dangling shows as dangling.
30 Note that users fetching over dumb protocols will have to fetch the
32 whole new pack in order to get any contained object, no matter how
33 many other objects in that pack they already have locally.
34 Promisor packfiles are repacked separately: if there are packfiles
36 that have an associated ".promisor" file, these packfiles will be
37 repacked into another separate pack, and an empty ".promisor" file
38 corresponding to the new separate pack will be written.
39 -A
41 Same as -a, unless -d is used. Then any unreachable objects in a
42 previous pack become loose, unpacked objects, instead of being left
43 in the old pack. Unreachable objects are never intentionally added
44 to a pack, even when repacking. This option prevents unreachable
45 objects from being immediately deleted by way of being left in the
46 old pack and then removed. Instead, the loose unreachable objects
47 will be pruned according to normal expiry rules with the next git
48 gc invocation. See git-gc(1).
49 -d
51 After packing, if the newly created packs make some existing packs
52 redundant, remove the redundant packs. Also run git prune-packed to
53 remove redundant loose object files.
54 -l
56 Pass the --local option to git pack-objects. See git-pack-
57 objects(1).
58 -f
60 Pass the --no-reuse-delta option to git-pack-objects, see git-pack-
61 objects(1).
62 -F
64 Pass the --no-reuse-object option to git-pack-objects, see git-
65 pack-objects(1).
66 -q
68 Pass the -q option to git pack-objects. See git-pack-objects(1).
69 -n
71 Do not update the server information with git update-server-info.
72 This option skips updating local catalog files needed to publish
73 this repository (or a direct copy of it) over HTTP or FTP. See git-
74 update-server-info(1).
75 --window=<n>, --depth=<n>
77 These two options affect how the objects contained in the pack are
78 stored using delta compression. The objects are first internally
79 sorted by type, size and optionally names and compared against the
80 other objects within --window to see if using delta compression
81 saves space. --depth limits the maximum delta depth; making it too
82 deep affects the performance on the unpacker side, because delta
83 data needs to be applied that many times to get to the necessary
84 object.
85 The default value for --window is 10 and --depth is 50. The maximum
87 depth is 4095.
88 --threads=<n>
90 This option is passed through to git pack-objects.
91 --window-memory=<n>
93 This option provides an additional limit on top of --window; the
94 window size will dynamically scale down so as to not take up more
95 than <n> bytes in memory. This is useful in repositories with a mix
96 of large and small objects to not run out of memory with a large
97 window, but still be able to take advantage of the large window for
98 the smaller objects. The size can be suffixed with "k", "m", or
99 "g". --window-memory=0 makes memory usage unlimited. The default
100 is taken from the pack.windowMemory configuration variable. Note
101 that the actual memory usage will be the limit multiplied by the
102 number of threads used by git-pack-objects(1).
103 --max-pack-size=<n>
105 Maximum size of each output pack file. The size can be suffixed
106 with "k", "m", or "g". The minimum size allowed is limited to 1
107 MiB. If specified, multiple packfiles may be created, which also
108 prevents the creation of a bitmap index. The default is unlimited,
109 unless the config variable pack.packSizeLimit is set. Note that
110 this option may result in a larger and slower repository; see the
111 discussion in pack.packSizeLimit.
112 -b, --write-bitmap-index
114 Write a reachability bitmap index as part of the repack. This only
115 makes sense when used with -a or -A, as the bitmaps must be able to
116 refer to all reachable objects. This option overrides the setting
117 of repack.writeBitmaps. This option has no effect if multiple
118 packfiles are created.
119 --pack-kept-objects
121 Include objects in .keep files when repacking. Note that we still
122 do not delete .keep packs after pack-objects finishes. This means
123 that we may duplicate objects, but this makes the option safe to
124 use when there are concurrent pushes or fetches. This option is
125 generally only useful if you are writing bitmaps with -b or
126 repack.writeBitmaps, as it ensures that the bitmapped packfile has
127 the necessary objects.
128 --keep-pack=<pack-name>
130 Exclude the given pack from repacking. This is the equivalent of
131 having .keep file on the pack. <pack-name> is the pack file name
132 without leading directory (e.g. pack-123.pack). The option could
133 be specified multiple times to keep multiple packs.
134 --unpack-unreachable=<when>
136 When loosening unreachable objects, do not bother loosening any
137 objects older than <when>. This can be used to optimize out the
138 write of any objects that would be immediately pruned by a
139 follow-up git prune.
140 -k, --keep-unreachable
142 When used with -ad, any unreachable objects from existing packs
143 will be appended to the end of the packfile instead of being
144 removed. In addition, any unreachable loose objects will be packed
145 (and their loose counterparts removed).
146 -i, --delta-islands
148 Pass the --delta-islands option to git-pack-objects, see git-pack-
149 objects(1).
150 -g=<factor>, --geometric=<factor>
152 Arrange resulting pack structure so that each successive pack
153 contains at least <factor> times the number of objects as the
154 next-largest pack.
155 git repack ensures this by determining a "cut" of packfiles that
157 need to be repacked into one in order to ensure a geometric
158 progression. It picks the smallest set of packfiles such that as
159 many of the larger packfiles (by count of objects contained in that
160 pack) may be left intact.
161 Unlike other repack modes, the set of objects to pack is determined
163 uniquely by the set of packs being "rolled-up"; in other words, the
164 packs determined to need to be combined in order to restore a
165 geometric progression.
166 When --unpacked is specified, loose objects are implicitly included
168 in this "roll-up", without respect to their reachability. This is
169 subject to change in the future. This option (implying a
170 drastically different repack mode) is not guaranteed to work with
171 all other combinations of option to git repack.
172
174 Various configuration variables affect packing, see git-config(1)
175 (search for "pack" and "delta").
176 By default, the command passes --delta-base-offset option to git
178 pack-objects; this typically results in slightly smaller packs, but the
179 generated packs are incompatible with versions of Git older than
180 version 1.4.4. If you need to share your repository with such ancient
181 Git versions, either directly or via the dumb http protocol, then you
182 need to set the configuration variable repack.UseDeltaBaseOffset to
183 "false" and repack. Access from old Git versions over the native
184 protocol is unaffected by this option as the conversion is performed on
185 the fly as needed in that case.
186 Delta compression is not used on objects larger than the
188 core.bigFileThreshold configuration variable and on files with the
189 attribute delta set to false.
190
192 git-pack-objects(1) git-prune-packed(1)
193
195 Part of the git(1) suite
196Git 2.33.1 2021-10-12 GIT-REPACK(1)