Git Repack Configuration and Advanced Options

--pack-kept-objects:: Include objects in `.keep` files when repacking. Note that we still do not delete `.keep` packs after `pack-objects` finishes. This means that we may duplicate objects, but this makes the option safe to use when there are concurrent pushes or fetches. This option is generally only useful if you are writing bitmaps with `-b` or `repack.writeBitmaps`, as it ensures that the bitmapped packfile has the necessary objects. --keep-pack=<pack-name>:: Exclude the given pack from repacking. This is the equivalent of having `.keep` file on the pack. `<pack-name>` is the pack file name without leading directory (e.g. `pack-123.pack`). The option can be specified multiple times to keep multiple packs. --unpack-unreachable=<when>:: When loosening unreachable objects, do not bother loosening any objects older than `<when>`. This can be used to optimize out the write of any objects that would be immediately pruned by a follow-up `git prune`. -k:: --keep-unreachable:: When used with `-ad`, any unreachable objects from existing packs will be appended to the end of the packfile instead of being removed. In addition, any unreachable loose objects will be packed (and their loose counterparts removed). -i:: --delta-islands:: Pass the `--delta-islands` option to `git-pack-objects`, see linkgit:git-pack-objects[1]. -g<factor>:: --geometric=<factor>:: Arrange resulting pack structure so that each successive pack contains at least `<factor>` times the number of objects as the next-largest pack. + `git repack` ensures this by determining a "cut" of packfiles that need to be repacked into one in order to ensure a geometric progression. It picks the smallest set of packfiles such that as many of the larger packfiles (by count of objects contained in that pack) may be left intact. + Unlike other repack modes, the set of objects to pack is determined uniquely by the set of packs being "rolled-up"; in other words, the packs determined to need to be combined in order to restore a geometric progression. + Loose objects are implicitly included in this "roll-up", without respect to their reachability. This is subject to change in the future. + When writing a multi-pack bitmap, `git repack` selects the largest resulting pack as the preferred pack for object selection by the MIDX (see linkgit:git-multi-pack-index[1]). -m:: --write-midx:: Write a multi-pack index (see linkgit:git-multi-pack-index[1]) containing the non-redundant packs. --name-hash-version=<n>:: Provide this argument to the underlying `git pack-objects` process. See linkgit:git-pack-objects[1] for full details. CONFIGURATION ------------- Various configuration variables affect packing, see linkgit:git-config[1] (search for "pack" and "delta"). By default, the command passes `--delta-base-offset` option to 'git pack-objects'; this typically results in slightly smaller packs, but the generated packs are incompatible with versions of Git older than version 1.4.4. If you need to share your repository with such ancient Git versions, either directly or via the dumb http protocol, then you need to set the configuration variable `repack.UseDeltaBaseOffset` to "false" and repack. Access from old Git versions over the native protocol is unaffected by this option as the conversion is performed on the fly as needed in that case. Delta compression is not used on objects larger than the `core.bigFileThreshold` configuration variable and on files with the attribute `delta` set to false. SEE ALSO -------- linkgit:git-pack-objects[1] linkgit:git-prune-packed[1] GIT --- Part of the linkgit:git[1] suite

The git-repack command offers various advanced options for customizing the repacking process, including options for packing unreachable objects, delta compression, and geometric pack structure, as well as configuration variables that affect packing, allowing for fine-grained control over repository optimization and compatibility with older Git versions.