Your company here ā€” click to reach over 10,000 unique daily visitors

git-multi-pack-index - Man Page

Write and verify multi-pack-indexes


git multi-pack-index [--object-dir=<dir>] [--[no-]bitmap] <sub-command>


Write or verify a multi-pack-index (MIDX) file.



Use given directory for the location of Git objects. We check <dir>/packs/multi-pack-index for the current MIDX file, and <dir>/packs for the pack-files to index.

<dir> must be an alternate of the current repository.


Turn progress on/off explicitly. If neither is specified, progress is shown if standard error is connected to a terminal. Supported by sub-commands write, verify, expire, and `repack.

The following subcommands are available:


Write a new MIDX file. The following options are available for the write sub-command:


Optionally specify the tie-breaking pack used when multiple packs contain the same object. <pack> must contain at least one object. If not given, ties are broken in favor of the pack with the lowest mtime.


Control whether or not a multi-pack bitmap is written.


Write a multi-pack index containing only the set of line-delimited pack index basenames provided over stdin.


With --bitmap, optionally specify a file which contains a "refs snapshot" taken prior to repacking.

A reference snapshot is composed of line-delimited OIDs corresponding to the reference tips, usually taken by git repack prior to generating a new pack. A line may optionally start with a + character to indicate that the reference which corresponds to that OID is "preferred" (see git-config(1)'s pack.preferBitmapTips.)

The file given at <path> is expected to be readable, and can contain duplicates. (If a given OID is given more than once, it is marked as preferred if at least one instance of it begins with the special + marker).


Verify the contents of the MIDX file.


Delete the pack-files that are tracked by the MIDX file, but have no objects referenced by the MIDX (with the exception of .keep packs and cruft packs). Rewrite the MIDX file afterward to remove all references to these pack-files.


Create a new pack-file containing objects in small pack-files referenced by the multi-pack-index. If the size given by the --batch-size=<size> argument is zero, then create a pack containing all objects referenced by the multi-pack-index. For a non-zero batch size, Select the pack-files by examining packs from oldest-to-newest, computing the "expected size" by counting the number of objects in the pack referenced by the multi-pack-index, then divide by the total number of objects in the pack and multiply by the pack size. We select packs with expected size below the batch size until the set of packs have total expected size at least the batch size, or all pack-files are considered. If only one pack-file is selected, then do nothing. If a new pack-file is created, rewrite the multi-pack-index to reference the new pack-file. A later run of git multi-pack-index expire will delete the pack-files that were part of this batch.

If repack.packKeptObjects is false, then any pack-files with an associated .keep file will not be selected for the batch to repack.


See Also

See The Multi-Pack-Index Design Document[1] and gitformat-pack(5) for more information on the multi-pack-index feature and its file format.


Part of the git(1) suite



The Multi-Pack-Index Design Document

Referenced By

git(1), git-config(1), git-maintenance(1), git-repack(1).

05/31/2024 Git 2.45.2 Git Manual