X-Git-Url: https://git.tokkee.org/?a=blobdiff_plain;f=Documentation%2Fgit-fetch-pack.txt;h=a99a5b321f763911b0d5d233a8135c5b60be6e3b;hb=660d579d6ff0ac29b8f7b38b3da73f09214d39aa;hp=884a26bbf352868806ce7f4d2c61deec9a40a822;hpb=07ee0d77c66d6f356cd3f82435e67510779aa53c;p=git.git diff --git a/Documentation/git-fetch-pack.txt b/Documentation/git-fetch-pack.txt index 884a26bbf..a99a5b321 100644 --- a/Documentation/git-fetch-pack.txt +++ b/Documentation/git-fetch-pack.txt @@ -1,47 +1,74 @@ git-fetch-pack(1) ================= -v0.1, July 2005 NAME ---- -git-fetch-pack - Receive missing objects from another repository. +git-fetch-pack - Receive missing objects from another repository SYNOPSIS -------- -git-fetch-pack [-q] [--exec=] [:] [...] < +'git-fetch-pack' [--all] [--quiet|-q] [--keep|-k] [--thin] [--upload-pack=] [--depth=] [--no-progress] [-v] [:] [...] DESCRIPTION ----------- +Usually you would want to use gitlink:git-fetch[1] which is a +higher level wrapper of this command instead. + Invokes 'git-upload-pack' on a potentially remote repository, and asks it to send objects missing from this repository, to update the named heads. The list of commits available locally -is fed from the standard input, to be sent to 'git-upload-pack' -running on the other end. +is found out by scanning local $GIT_DIR/refs/ and sent to +'git-upload-pack' running on the other end. -This command can be used only when the local side has a common -(ancestor) commit with the remote head that is being pulled -from. Use 'git-clone-pack' for that. +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 ------- --q:: +\--all:: + Fetch all remote refs. + +\--quiet, \-q:: Pass '-q' flag to 'git-unpack-objects'; this makes the cloning process less verbose. ---exec=:: +\--keep, \-k:: + 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. + +\--thin:: + Spend extra cycles to minimize the number of objects to be sent. + Use it on slower connection. + +\--upload-pack=:: 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 + 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). +\--exec=:: + Same as \--upload-pack=. + +\--depth=:: + Limit fetching to ancestor-chains not longer than n. + +\--no-progress:: + Do not show the progress. + +\-v:: + Run verbosely. + :: A remote host that houses the repository. When this part is specified, 'git-upload-pack' is invoked via @@ -50,15 +77,11 @@ OPTIONS :: 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. - However the program refuses to work if more than one - remote head matches the specified heads. I am not sure - what this means... Help!!!!! - Author ------ @@ -70,4 +93,4 @@ Documentation by Junio C Hamano. GIT --- -Part of the link:git.html[git] suite +Part of the gitlink:git[7] suite