GIT-INDEX-PACK(1) Git Manual GIT-INDEX-PACK(1)NAME
git-index-pack - Build pack index file for an existing packed archive
SYNOPSIS
git index-pack [-v] [-o <index-file>] <pack-file>
git index-pack --stdin [--fix-thin] [--keep] [-v] [-o <index-file>]
[<pack-file>]
DESCRIPTION
Reads a packed archive (.pack) from the specified file, and builds a pack index file (.idx) for it. The packed archive together with the
pack index can then be placed in the objects/pack/ directory of a Git repository.
OPTIONS -v
Be verbose about what is going on, including progress status.
-o <index-file>
Write the generated pack index into the specified file. Without this option the name of pack index file is constructed from the name of
packed archive file by replacing .pack with .idx (and the program fails if the name of packed archive does not end with .pack).
--stdin
When this flag is provided, the pack is read from stdin instead and a copy is then written to <pack-file>. If <pack-file> is not
specified, the pack is written to objects/pack/ directory of the current Git repository with a default name determined from the pack
content. If <pack-file> is not specified consider using --keep to prevent a race condition between this process and git repack.
--fix-thin
Fix a "thin" pack produced by git pack-objects --thin (see git-pack-objects(1) for details) by adding the excluded objects the
deltified objects are based on to the pack. This option only makes sense in conjunction with --stdin.
--keep
Before moving the index into its final destination create an empty .keep file for the associated pack file. This option is usually
necessary with --stdin to prevent a simultaneous git repack process from deleting the newly constructed pack and index before refs can
be updated to use objects contained in the pack.
--keep=<msg>
Like --keep create a .keep file before moving the index into its final destination, but rather than creating an empty file place <msg>
followed by an LF into the .keep file. The <msg> message can later be searched for within all .keep files to locate any which have
outlived their usefulness.
--index-version=<version>[,<offset>]
This is intended to be used by the test suite only. It allows to force the version for the generated pack index, and to force 64-bit
index entries on objects located above the given offset.
--strict
Die, if the pack contains broken objects or links.
--check-self-contained-and-connected
Die if the pack contains broken links. For internal use only.
--threads=<n>
Specifies the number of threads to spawn when resolving deltas. This requires that index-pack be compiled with pthreads otherwise this
option is ignored with a warning. This is meant to reduce packing time on multiprocessor machines. The required amount of memory for
the delta search window is however multiplied by the number of threads. Specifying 0 will cause Git to auto-detect the number of CPU's
and use maximum 3 threads.
NOTE
Once the index has been created, the list of object names is sorted and the SHA-1 hash of that list is printed to stdout. If --stdin was
also used then this is prefixed by either "pack ", or "keep " if a new .keep file was successfully created. This is useful to remove a
.keep file used as a lock to prevent the race with git repack mentioned above.
GIT
Part of the git(1) suite
Git 1.8.5.3 01/14/2014 GIT-INDEX-PACK(1)
Check Out this Related Man Page
GIT-REPACK(1) Git Manual GIT-REPACK(1)NAME
git-repack - Pack unpacked objects in a repository
SYNOPSIS
git repack [-a] [-A] [-d] [-f] [-F] [-l] [-n] [-q] [--window=<n>] [--depth=<n>]
DESCRIPTION
This script is used to combine all objects that do not currently reside in a "pack", into a pack. It can also be used to re-organize
existing packs into a single, more efficient pack.
A pack is a collection of objects, individually compressed, with delta compression applied, stored in a single file, with an associated
index file.
Packs are used to reduce the load on mirror systems, backup engines, disk storage, etc.
OPTIONS -a
Instead of incrementally packing the unpacked objects, pack everything referenced into a single pack. Especially useful when packing a
repository that is used for private development. Use with -d. This will clean up the objects that git prune leaves behind, 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, no matter 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 being left in
the old pack. Unreachable objects are never intentionally added to a pack, even when repacking. This option prevents unreachable
objects from being immediately deleted by way of being left in the old pack and then removed. Instead, the loose unreachable 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 git prune-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 to publish this
repository (or a direct copy of it) over HTTP or FTP. See git-update-server-info(1).
--window=<n>, --depth=<n>
These two options affect how the objects contained in the pack are stored using delta compression. The objects are first internally
sorted by type, size and optionally names and compared against the other objects within --window to see if using delta compression
saves space. --depth limits the maximum delta depth; making it too deep affects the performance on the unpacker side, because delta
data needs to be applied that many times to get to the necessary object. The default value for --window is 10 and --depth is 50.
--window-memory=<n>
This option provides an additional limit on top of --window; the window size will dynamically scale down so as to not take up more than
<n> bytes in memory. This is useful in repositories with a mix of large and small objects to not run out of memory with a 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, which is the default.
--max-pack-size=<n>
Maximum size of each output pack file. The size can be suffixed with "k", "m", or "g". The minimum size allowed is limited to 1 MiB. If
specified, multiple packfiles may be created. The default is unlimited, unless the config variable pack.packSizeLimit is set.
CONFIGURATION
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 or rsync 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.
SEE ALSO git-pack-objects(1)git-prune-packed(1)GIT
Part of the git(1) suite
Git 1.8.3.1 06/10/2014 GIT-REPACK(1)