-a

Instead of incrementally packing the unpacked objects, pack everything referenced into a single pack. Especially useful whenpacking a repository that is used for private development. Use with -d. This will clean up the objects that git prune leavesbehind, but git fsck --full --dangling shows as dangling.Note that users fetching over dumb protocols will have to fetch the whole new pack in order to get any contained object, nomatter how many other objects in that pack they already have locally.

-A

Same as -a, unless -d is used. Then any unreachable objects in a previous pack become loose, unpacked objects, instead of beingleft in the old pack. Unreachable objects are never intentionally added to a pack, even when repacking. This option preventsunreachable objects from being immediately deleted by way of being left in the old pack and then removed. Instead, the looseunreachable objects will be pruned according to normal expiry rules with the next git gc invocation. See git-gc(1).

-d

After packing, if the newly created packs make some existing packs redundant, remove the redundant packs. Also run gitprune-packed to remove redundant loose object files.

-l

Pass the --local option to git pack-objects. See git-pack-objects(1).

-f

Pass the --no-reuse-delta option to git-pack-objects, see git-pack-objects(1).

-F

Pass the --no-reuse-object option to git-pack-objects, see git-pack-objects(1).

-q

Pass the -q option to git pack-objects. See git-pack-objects(1).

-n

Do not update the server information with git update-server-info. This option skips updating local catalog files needed topublish this repository (or a direct copy of it) over HTTP or FTP. See git-update-server-info(1).

--window

These two options affect how the objects contained in the pack are stored using delta compression. The objects are firstinternally sorted by type, size and optionally names and compared against the other objects within --window to see if using deltacompression saves space. --depth limits the maximum delta depth; making it too deep affects the performance on the unpackerside, because delta data needs to be applied that many times to get to the necessary object. The default value for --window is 10and --depth is 50.

--threads

This option is passed through to git pack-objects.

--window-memory

This option provides an additional limit on top of --window; the window size will dynamically scale down so as to not take upmore than <n> bytes in memory. This is useful in repositories with a mix of large and small objects to not run out of memory witha large window, but still be able to take advantage of the large window for the smaller objects. The size can be suffixed with"k", "m", or "g". --window-memory=0 makes memory usage unlimited. The default is taken from the pack.windowMemory configurationvariable. Note that the actual memory usage will be the limit multiplied by the number of threads used by git-pack-objects(1).

--max-pack-size

Maximum size of each output pack file. The size can be suffixed with "k", "m", or "g". The minimum size allowed is limited to 1MiB. If specified, multiple packfiles may be created, which also prevents the creation of a bitmap index. The default isunlimited, unless the config variable pack.packSizeLimit is set.

-b

Write a reachability bitmap index as part of the repack. This only makes sense when used with -a or -A, as the bitmaps must beable to refer to all reachable objects. This option overrides the setting of repack.writeBitmaps. This option has no effect ifmultiple packfiles are created.

--pack-kept-objects

Include objects in .keep files when repacking. Note that we still do not delete .keep packs after pack-objects finishes. Thismeans that we may duplicate objects, but this makes the option safe to use when there are concurrent pushes or fetches. Thisoption is generally only useful if you are writing bitmaps with -b or repack.writeBitmaps, as it ensures that the bitmappedpackfile has the necessary objects.

--unpack-unreachable

When loosening unreachable objects, do not bother loosening any objects older than <when>. This can be used to optimize out thewrite of any objects that would be immediately pruned by a follow-up git prune.

-k

When used with -ad, any unreachable objects from existing packs will be appended to the end of the packfile instead of beingremoved. In addition, any unreachable loose objects will be packed (and their loose counterparts removed).CONFIGURATIONBy default, the command passes --delta-base-offset option to git pack-objects; this typically results in slightly smaller packs, butthe generated packs are incompatible with versions of Git older than version 1.4.4. If you need to share your repository with suchancient Git versions, either directly or via the dumb http protocol, then you need to set the configuration variablerepack.UseDeltaBaseOffset to "false" and repack. Access from old Git versions over the native protocol is unaffected by this optionas the conversion is performed on the fly as needed in that case.