GIT\-FETCH\-PACKSection: Git Manual (1)
Index Return to Main Contents
NAMEgit-fetch-pack - Receive missing objects from another repository
SYNOPSISgit-fetch-pack [--all] [--quiet|-q] [--keep|-k] [--thin] [--upload-pack=<git-upload-pack>] [--depth=<n>] [--no-progress] [-v] [<host>:]<directory> [<refs>...]
DESCRIPTIONUsually you would want to use git-fetch(1) which is a higher level wrapper of this command instead.
Invokes git-upload-pack on a potentially 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 local $GIT_DIR/refs/ and sent to git-upload-pack running on the other end.
- Fetch all remote refs.
- Pass -q flag to git-unpack-objects; this makes the cloning process less verbose.
- 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.
- Spend extra cycles to minimize the number of objects to be sent. Use it on slower connection.
- 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).
- Same as --upload-pack=<git-upload-pack>.
- Limit fetching to ancestor-chains not longer than n.
- Do not show the progress.
- Run verbosely.
- A remote host that houses the repository. When this part is specified, git-upload-pack is invoked via ssh.
- The repository to sync from.
- 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.
AUTHORWritten by Linus Torvalds <firstname.lastname@example.org>
DOCUMENTATIONDocumentation by Junio C Hamano.
GITPart of the git(7) suite