Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 188.8.131.52 → 1.9.0 no changes
- 1.8.4 08/23/13
- 184.108.40.206 → 220.127.116.11 no changes
- 18.104.22.168 04/26/13
- 22.214.171.124 04/07/13
- 126.96.36.199 → 188.8.131.52 no changes
- 1.7.11 06/17/12
- 184.108.40.206 → 220.127.116.11 no changes
- 1.7.5 04/24/11
- 18.104.22.168 → 22.214.171.124 no changes
- 126.96.36.199 10/22/10
- 188.8.131.52 → 184.108.40.206 no changes
- 220.127.116.11 02/28/10
- 1.7.0 02/12/10
- 18.104.22.168 → 22.214.171.124 no changes
- 1.6.0 08/17/08
- 126.96.36.199 → 188.8.131.52 no changes
- 1.5.6 06/18/08
- 184.108.40.206 → 220.127.116.11 no changes
- 1.5.5 04/08/08
git-index-pack(1) Manual Page
git-index-pack - Build pack index file for an existing packed archive
git-index-pack [-v] [-o <index-file>] <pack-file> git-index-pack --stdin [--fix-thin] [--keep] [-v] [-o <index-file>] [<pack-file>]
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.
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).
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(1).
It is possible for git-pack-objects(1) to build "thin" pack, which records objects in deltified form based on objects not included in the pack to reduce network traffic. Those objects are expected to be present on the receiving end and they must be included in the pack for that pack to be self contained and indexable. Without this option any attempt to index a thin pack will fail. This option only makes sense in conjunction with --stdin.
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(1) process from deleting the newly constructed pack and index before refs can be updated to use objects contained in the pack.
Like --keep create a .keep file before moving the index into its final destination, but rather than creating an empty file place why followed by an LF into the .keep file. The why message can later be searched for within all .keep files to locate any which have outlived their usefulness.
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.
Die, if the pack contains broken objects or links.
Once the index has been created, the list of object names is sorted and the SHA1 hash of that list is printed to stdout. If --stdin was also used then this is prefixed by either "pack\t", or "keep\t" 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(1) mentioned above.
Written by Sergey Vlasov <firstname.lastname@example.org>
Documentation by Sergey Vlasov
Part of the git(1) suite