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' [--all] [--quiet|-q] [--keep|-k] [--thin] [--include-tag] [--upload-pack=<git-upload-pack>] [--depth=<n>] [--no-progress] [-v] [<host>:]<directory> [<refs>...] 12 13DESCRIPTION 14----------- 15Usually you would want to use linkgit:git-fetch[1] which is a 16higher level wrapper of this command instead. 17 18Invokes 'git-upload-pack' on a potentially remote repository, 19and asks it to send objects missing from this repository, to 20update the named heads. The list of commits available locally 21is found out by scanning local $GIT_DIR/refs/ and sent to 22'git-upload-pack' running on the other end. 23 24This command degenerates to download everything to complete the 25asked refs from the remote side when the local side does not 26have a common ancestor commit. 27 28 29OPTIONS 30------- 31\--all:: 32 Fetch all remote refs. 33 34\--quiet, \-q:: 35 Pass '-q' flag to 'git-unpack-objects'; this makes the 36 cloning process less verbose. 37 38\--keep, \-k:: 39 Do not invoke 'git-unpack-objects' on received data, but 40 create a single packfile out of it instead, and store it 41 in the object database. If provided twice then the pack is 42 locked against repacking. 43 44\--thin:: 45 Spend extra cycles to minimize the number of objects to be sent. 46 Use it on slower connection. 47 48\--include-tag:: 49 If the remote side supports it, annotated tags objects will 50 be downloaded on the same connection as the other objects if 51 the object the tag references is downloaded. The caller must 52 otherwise determine the tags this option made available. 53 54\--upload-pack=<git-upload-pack>:: 55 Use this to specify the path to 'git-upload-pack' on the 56 remote side, if is not found on your $PATH. 57 Installations of sshd ignores the user's environment 58 setup scripts for login shells (e.g. .bash_profile) and 59 your privately installed git may not be found on the system 60 default $PATH. Another workaround suggested is to set 61 up your $PATH in ".bashrc", but this flag is for people 62 who do not want to pay the overhead for non-interactive 63 shells by having a lean .bashrc file (they set most of 64 the things up in .bash_profile). 65 66\--exec=<git-upload-pack>:: 67 Same as \--upload-pack=<git-upload-pack>. 68 69\--depth=<n>:: 70 Limit fetching to ancestor-chains not longer than n. 71 72\--no-progress:: 73 Do not show the progress. 74 75\-v:: 76 Run verbosely. 77 78<host>:: 79 A remote host that houses the repository. When this 80 part is specified, 'git-upload-pack' is invoked via 81 ssh. 82 83<directory>:: 84 The repository to sync from. 85 86<refs>...:: 87 The remote heads to update from. This is relative to 88 $GIT_DIR (e.g. "HEAD", "refs/heads/master"). When 89 unspecified, update from all heads the remote side has. 90 91 92Author 93------ 94Written by Linus Torvalds <torvalds@osdl.org> 95 96Documentation 97-------------- 98Documentation by Junio C Hamano. 99 100GIT 101--- 102Part of the linkgit:git[7] suite