Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 18.104.22.168 → 1.9.0 no changes
- 1.8.5 11/27/13
- 22.214.171.124 → 126.96.36.199 no changes
- 1.7.10 04/06/12
- 188.8.131.52 → 184.108.40.206 no changes
- 220.127.116.11 08/24/11
- 18.104.22.168 → 1.7.6 no changes
- 1.7.5 04/24/11
- 22.214.171.124 → 126.96.36.199 no changes
- 188.8.131.52 12/03/10
- 184.108.40.206 10/22/10
- 220.127.116.11 → 18.104.22.168 no changes
- 1.7.0 02/12/10
- 22.214.171.124 → 126.96.36.199 no changes
- 1.6.4 07/29/09
- 188.8.131.52 → 184.108.40.206 no changes
- 220.127.116.11 12/07/08
- 18.104.22.168 no changes
- 22.214.171.124 10/21/08
- 126.96.36.199 → 188.8.131.52 no changes
git-repack(1) Manual Page
git-repack - Pack unpacked objects in a repository
git repack [-a] [-A] [-d] [-f] [-l] [-n] [-q] [--window=N] [--depth=N]
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.
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 and there is no need to worry about people fetching via dumb protocols from it. Use with -d. This will clean up the objects that git prune leaves behind, but git fsck --full shows as dangling.
Same as -a, but 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. When used with -d, 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).
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.
Pass the --local option to git-pack-objects. See git-pack-objects(1).
Pass the --no-reuse-delta option to git-pack-objects. See git-pack-objects(1).
Pass the -q option to git-pack-objects. See git-pack-objects(1).
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).
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.
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.
Maximum size of each output packfile, expressed in MiB. If specified, multiple packfiles may be created. The default is unlimited.
When configuration variable repack.UseDeltaBaseOffset is set for the repository, 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 (and including) v1.4.3; do not set the variable in a repository that older version of git needs to be able to read (this includes repositories from which packs can be copied out over http or rsync, and people who obtained packs that way can try to use older git with it).
Written by Linus Torvalds <email@example.com>
Documentation by Ryan Anderson <firstname.lastname@example.org>
Part of the git(1) suite