Mac Developer Library Developer


This manual page is part of Xcode Tools version 5.0

To obtain these tools:

If you are running a version of Xcode Tools other than 5.0, view the documentation locally:

  • In Xcode

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • To learn how the manual is organized or to learn about command syntax, read the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Developer Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.

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

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

       git fetch-pack [--all] [--quiet|-q] [--keep|-k] [--thin] [--include-tag]
               [--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

           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

       -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

           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.  git-upload-pack treats the special depth
           2147483647 as infinite even if there is an ancestor-chain that long.

           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.

       Part of the git(1) suite

Git 1.8.3                                        05/24/2013                                GIT-FETCH-PACK(1)

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.