Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 126.96.36.199 → 1.9.0 no changes
- 188.8.131.52 12/17/13
- 184.108.40.206 no changes
- 1.8.5 11/27/13
- 220.127.116.11 → 18.104.22.168 no changes
- 1.8.3 05/24/13
- 22.214.171.124 → 126.96.36.199 no changes
- 188.8.131.52 04/07/13
- 1.8.1 → 184.108.40.206 no changes
- 220.127.116.11 12/27/12
- 18.104.22.168 → 22.214.171.124 no changes
- 126.96.36.199 05/02/12
- 188.8.131.52 → 1.7.10 no changes
- 184.108.40.206 08/24/11
- 220.127.116.11 → 1.7.6 no changes
- 1.7.5 04/24/11
- 18.104.22.168 → 22.214.171.124 no changes
- 126.96.36.199 02/28/10
- 1.7.0 02/12/10
- 188.8.131.52 → 184.108.40.206 no changes
git-fetch-pack(1) Manual Page
git-fetch-pack - Receive missing objects from another repository
git fetch-pack [--all] [--quiet|-q] [--keep|-k] [--thin] [--include-tag] [--upload-pack=<git-upload-pack>] [--depth=<n>] [--no-progress] [-v] [<host>:]<directory> [<refs>...]
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.
Fetch all remote refs.
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.
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.
Fetch a "thin" pack, which records objects in deltified form based on objects not included in the pack to reduce network traffic.
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.
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.
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.
Part of the git(1) suite