NAME
git-fetch-pack - Receive missing objects from another repository
SYNOPSIS
git fetch-pack\n [--all] [--quiet|-q] [--keep|-k] [--thin] [--include-tag]
\n
[--upload-pack=<git-upload-pack>]
\n
[--depth=<n>] [--no-progress]
\n
[-v] <repository> [<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
--stdin
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
-k, --keep
--thin
--include-tag
--upload-pack=<git-upload-pack>
--exec=<git-upload-pack>
--depth=<n>
--shallow-since=<date>
--shallow-exclude=<revision>
--deepen-relative
--refetch
--no-progress
--check-self-contained-and-connected
-v
<repository>
<refs>...
If the remote has enabled the options uploadpack.allowTipSHA1InWant, uploadpack.allowReachableSHA1InWant, or uploadpack.allowAnySHA1InWant, they may alternatively be 40-hex sha1s present on the remote.
SEE ALSO
git-fetch(1)
GIT
Part of the git(1) suite