Setup and Config
Getting and Creating Projects
Basic Snapshotting
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
Patching
Debugging
External Systems
Server Admin
Guides
- gitattributes
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- Glossary
- Hooks
- gitignore
- gitmodules
- Revisions
- Submodules
- Tutorial
- Workflows
- All guides...
Administration
Plumbing Commands
-
2.47.0
10/06/24
- 2.38.3 → 2.46.2 no changes
-
2.38.2
12/11/22
- 2.38.1 no changes
-
2.38.0
10/02/22
- 2.34.1 → 2.37.7 no changes
-
2.34.0
11/15/21
- 2.32.1 → 2.33.8 no changes
-
2.32.0
06/06/21
- 2.29.1 → 2.31.8 no changes
-
2.29.0
10/19/20
- 2.27.1 → 2.28.1 no changes
-
2.27.0
06/01/20
- 2.25.1 → 2.26.3 no changes
-
2.25.0
01/13/20
- 2.23.1 → 2.24.4 no changes
-
2.23.0
08/16/19
- 2.20.1 → 2.22.5 no changes
-
2.20.0
12/09/18
SYNOPSIS
git multi-pack-index [--object-dir=<dir>] [--[no-]progress] [--preferred-pack=<pack>] <subcommand>
OPTIONS
- --object-dir=<dir>
-
Use given directory for the location of Git objects. We check
<dir>/packs/multi-pack-indexfor the current MIDX file, and<dir>/packsfor the pack-files to index. - --[no-]progress
-
Turn progress on/off explicitly. If neither is specified, progress is shown if standard error is connected to a terminal.
The following subcommands are available:
- write
-
Write a new MIDX file. The following options are available for the
writesub-command: - verify
-
Verify the contents of the MIDX file.
- expire
-
Delete the pack-files that are tracked by the MIDX file, but have no objects referenced by the MIDX. Rewrite the MIDX file afterward to remove all references to these pack-files.
- repack
-
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.packKeptObjectsisfalse, then any pack-files with an associated.keepfile will not be selected for the batch to repack.
EXAMPLES
-
Write a MIDX file for the packfiles in the current .git folder.
$ git multi-pack-index write
-
Write a MIDX file for the packfiles in an alternate object store.
$ git multi-pack-index --object-dir <alt> write
-
Verify the MIDX file for the packfiles in the current .git folder.
$ git multi-pack-index verify
SEE ALSO
See The Multi-Pack-Index Design Document and The Multi-Pack-Index Format for more information on the multi-pack-index feature.
GIT
Part of the git[1] suite
