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
13 This command is used to combine all objects that do not currently
14 reside in a "pack", into a pack. It can also be used to re-organize
15 existing packs into a single, more efficient pack.
16 A pack is a collection of objects, individually compressed, with delta
18 compression applied, stored in a single file, with an associated index
19 file.
20 Packs are used to reduce the load on mirror systems, backup engines,
22 disk storage, etc.
23
25 -a
26 Instead of incrementally packing the unpacked objects, pack
27 everything referenced into a single pack. Especially useful when
28 packing a repository that is used for private development. Use with
29 -d. This will clean up the objects that git prune leaves behind,
30 but git fsck --full --dangling shows as dangling.
31 Note that users fetching over dumb protocols will have to fetch the
33 whole new pack in order to get any contained object, no matter how
34 many other objects in that pack they already have locally.
35 -A
37 Same as -a, unless -d is used. Then any unreachable objects in a
38 previous pack become loose, unpacked objects, instead of being left
39 in the old pack. Unreachable objects are never intentionally added
40 to a pack, even when repacking. This option prevents unreachable
41 objects from being immediately deleted by way of being left in the
42 old pack and then removed. Instead, the loose unreachable objects
43 will be pruned according to normal expiry rules with the next git
44 gc invocation. See git-gc(1).
45 -d
47 After packing, if the newly created packs make some existing packs
48 redundant, remove the redundant packs. Also run git prune-packed to
49 remove redundant loose object files.
50 -l
52 Pass the --local option to git pack-objects. See git-pack-
53 objects(1).
54 -f
56 Pass the --no-reuse-delta option to git-pack-objects, see git-pack-
57 objects(1).
58 -F
60 Pass the --no-reuse-object option to git-pack-objects, see git-
61 pack-objects(1).
62 -q
64 Pass the -q option to git pack-objects. See git-pack-objects(1).
65 -n
67 Do not update the server information with git update-server-info.
68 This option skips updating local catalog files needed to publish
69 this repository (or a direct copy of it) over HTTP or FTP. See git-
70 update-server-info(1).
71 --window=<n>, --depth=<n>
73 These two options affect how the objects contained in the pack are
74 stored using delta compression. The objects are first internally
75 sorted by type, size and optionally names and compared against the
76 other objects within --window to see if using delta compression
77 saves space. --depth limits the maximum delta depth; making it too
78 deep affects the performance on the unpacker side, because delta
79 data needs to be applied that many times to get to the necessary
80 object.
81 The default value for --window is 10 and --depth is 50. The maximum
83 depth is 4095.
84 --threads=<n>
86 This option is passed through to git pack-objects.
87 --window-memory=<n>
89 This option provides an additional limit on top of --window; the
90 window size will dynamically scale down so as to not take up more
91 than <n> bytes in memory. This is useful in repositories with a mix
92 of large and small objects to not run out of memory with a large
93 window, but still be able to take advantage of the large window for
94 the smaller objects. The size can be suffixed with "k", "m", or
95 "g". --window-memory=0 makes memory usage unlimited. The default
96 is taken from the pack.windowMemory configuration variable. Note
97 that the actual memory usage will be the limit multiplied by the
98 number of threads used by git-pack-objects(1).
99 --max-pack-size=<n>
101 Maximum size of each output pack file. The size can be suffixed
102 with "k", "m", or "g". The minimum size allowed is limited to 1
103 MiB. If specified, multiple packfiles may be created, which also
104 prevents the creation of a bitmap index. The default is unlimited,
105 unless the config variable pack.packSizeLimit is set.
106 -b, --write-bitmap-index
108 Write a reachability bitmap index as part of the repack. This only
109 makes sense when used with -a or -A, as the bitmaps must be able to
110 refer to all reachable objects. This option overrides the setting
111 of repack.writeBitmaps. This option has no effect if multiple
112 packfiles are created.
113 --pack-kept-objects
115 Include objects in .keep files when repacking. Note that we still
116 do not delete .keep packs after pack-objects finishes. This means
117 that we may duplicate objects, but this makes the option safe to
118 use when there are concurrent pushes or fetches. This option is
119 generally only useful if you are writing bitmaps with -b or
120 repack.writeBitmaps, as it ensures that the bitmapped packfile has
121 the necessary objects.
122 --keep-pack=<pack-name>
124 Exclude the given pack from repacking. This is the equivalent of
125 having .keep file on the pack. <pack-name> is the the pack file
126 name without leading directory (e.g. pack-123.pack). The option
127 could be specified multiple times to keep multiple packs.
128 --unpack-unreachable=<when>
130 When loosening unreachable objects, do not bother loosening any
131 objects older than <when>. This can be used to optimize out the
132 write of any objects that would be immediately pruned by a
133 follow-up git prune.
134 -k, --keep-unreachable
136 When used with -ad, any unreachable objects from existing packs
137 will be appended to the end of the packfile instead of being
138 removed. In addition, any unreachable loose objects will be packed
139 (and their loose counterparts removed).
140
142 By default, the command passes --delta-base-offset option to git
143 pack-objects; this typically results in slightly smaller packs, but the
144 generated packs are incompatible with versions of Git older than
145 version 1.4.4. If you need to share your repository with such ancient
146 Git versions, either directly or via the dumb http protocol, then you
147 need to set the configuration variable repack.UseDeltaBaseOffset to
148 "false" and repack. Access from old Git versions over the native
149 protocol is unaffected by this option as the conversion is performed on
150 the fly as needed in that case.
151
153 git-pack-objects(1) git-prune-packed(1)
154
156 Part of the git(1) suite
157Git 2.18.1 05/14/2019 GIT-REPACK(1)