git-index-pack(1) [suse man page]

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=why
	   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.

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

NOTE

       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	", 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.

AUTHOR

       Written by Sergey Vlasov <vsu@altlinux.ru[1]>

DOCUMENTATION

       Documentation by Sergey Vlasov

GIT

       Part of the git(1) suite

NOTES

	1. vsu@altlinux.ru
	   mailto:vsu@altlinux.ru

Git 1.7.1							    07/05/2010							 GIT-INDEX-PACK(1)

GIT-FETCH-PACK(1)						    Git Manual							 GIT-FETCH-PACK(1)

NAME

       git-fetch-pack - Receive missing objects from another repository

SYNOPSIS

       git fetch-pack [--all] [--quiet|-q] [--keep|-k] [--thin] [--include-tag] [--upload-pack=<git-upload-pack>] [--depth=<n>] [--no-progress] [-v] [<host>:]<directory> [<refs>...]

DESCRIPTION

       Usually you would want to use git fetch, which is a higher level wrapper of this command, instead.

       Invokes git-upload-pack on a possibly remote repository and asks it to send objects missing from this repository, to update the named
       heads. The list of commits available locally is found out by scanning the local refs/ hierarchy and sent to git-upload-pack running on the
       other end.

       This command degenerates to download everything to complete the asked refs from the remote side when the local side does not have a common
       ancestor commit.

OPTIONS

       --all
	   Fetch all remote refs.

       --stdin
	   Take the list of refs from stdin, one per line. If there are refs specified on the command line in addition to this option, then the
	   refs from stdin are processed after those on the command line.

	   If --stateless-rpc is specified together with this option then the list of refs must be in packet format (pkt-line). Each ref must be
	   in a separate packet, and the list must end with a flush packet.

       -q, --quiet
	   Pass -q flag to git unpack-objects; this makes the cloning process less verbose.

       -k, --keep
	   Do not invoke git unpack-objects on received data, but create a single packfile out of it instead, and store it in the object database.
	   If provided twice then the pack is locked against repacking.

       --thin
	   Fetch a "thin" pack, which records objects in deltified form based on objects not included in the pack to reduce network traffic.

       --include-tag
	   If the remote side supports it, annotated tags objects will be downloaded on the same connection as the other objects if the object the
	   tag references is downloaded. The caller must otherwise determine the tags this option made available.

       --upload-pack=<git-upload-pack>
	   Use this to specify the path to git-upload-pack on the remote side, if is not found on your $PATH. Installations of sshd ignores the
	   user's environment setup scripts for login shells (e.g. .bash_profile) and your privately installed git may not be found on the system
	   default $PATH. Another workaround suggested is to set up your $PATH in ".bashrc", but this flag is for people who do not want to pay
	   the overhead for non-interactive shells by having a lean .bashrc file (they set most of the things up in .bash_profile).

       --exec=<git-upload-pack>
	   Same as --upload-pack=<git-upload-pack>.

       --depth=<n>
	   Limit fetching to ancestor-chains not longer than n.

       --no-progress
	   Do not show the progress.

       -v
	   Run verbosely.

       <host>
	   A remote host that houses the repository. When this part is specified, git-upload-pack is invoked via ssh.

       <directory>
	   The repository to sync from.

       <refs>...
	   The remote heads to update from. This is relative to $GIT_DIR (e.g. "HEAD", "refs/heads/master"). When unspecified, update from all
	   heads the remote side has.

GIT

       Part of the git(1) suite

Git 1.7.10.4							    11/24/2012							 GIT-FETCH-PACK(1)