Documentation / git-fetch-pack.txton commit Merge git://git.kernel.org/pub/scm/gitk/gitk (3d990f1)
   1git-fetch-pack(1)
   2=================
   3
   4NAME
   5----
   6git-fetch-pack - Receive missing objects from another repository
   7
   8
   9SYNOPSIS
  10--------
  11'git-fetch-pack' [-q] [-k] [--exec=<git-upload-pack>] [<host>:]<directory> [<refs>...]
  12
  13DESCRIPTION
  14-----------
  15Invokes 'git-upload-pack' on a potentially remote repository,
  16and asks it to send objects missing from this repository, to
  17update the named heads.  The list of commits available locally
  18is found out by scanning local $GIT_DIR/refs/ and sent to
  19'git-upload-pack' running on the other end.
  20
  21This command degenerates to download everything to complete the
  22asked refs from the remote side when the local side does not
  23have a common ancestor commit.
  24
  25
  26OPTIONS
  27-------
  28-q::
  29        Pass '-q' flag to 'git-unpack-objects'; this makes the
  30        cloning process less verbose.
  31
  32-k::
  33        Do not invoke 'git-unpack-objects' on received data, but
  34        create a single packfile out of it instead, and store it
  35        in the object database.
  36
  37--exec=<git-upload-pack>::
  38        Use this to specify the path to 'git-upload-pack' on the
  39        remote side, if is not found on your $PATH.
  40        Installations of sshd ignores the user's environment
  41        setup scripts for login shells (e.g. .bash_profile) and
  42        your privately installed git may not be found on the system
  43        default $PATH.  Another workaround suggested is to set
  44        up your $PATH in ".bashrc", but this flag is for people
  45        who do not want to pay the overhead for non-interactive
  46        shells by having a lean .bashrc file (they set most of
  47        the things up in .bash_profile).
  48
  49<host>::
  50        A remote host that houses the repository.  When this
  51        part is specified, 'git-upload-pack' is invoked via
  52        ssh.
  53
  54<directory>::
  55        The repository to sync from.
  56
  57<refs>...::
  58        The remote heads to update from. This is relative to
  59        $GIT_DIR (e.g. "HEAD", "refs/heads/master").  When
  60        unspecified, update from all heads the remote side has.
  61
  62
  63Author
  64------
  65Written by Linus Torvalds <torvalds@osdl.org>
  66
  67Documentation
  68--------------
  69Documentation by Junio C Hamano.
  70
  71GIT
  72---
  73Part of the gitlink:git[7] suite