Not implemented It is possible for 'git-pack-objects' 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.

Not implemented 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.

Not implemented 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.

Not implemented 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.

Not implemented 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).

Not implemented When this flag is provided, the pack is read from stdin instead and a copy is then written to . If 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 is not specified consider using --keep to prevent a race condition between this process and 'git-repack'.

Not implemented Die, if the pack contains broken objects or links.

Not implemented Be verbose about what is going on, including progress status.