1git-clone-pack(1) 2================= 3 4NAME 5---- 6git-clone-pack - Clones a repository by receiving packed objects. 7 8 9SYNOPSIS 10-------- 11'git-clone-pack' [--exec=<git-upload-pack>] [<host>:]<directory> [<head>...] 12 13DESCRIPTION 14----------- 15Clones a repository into the current repository by invoking 16'git-upload-pack', possibly on the remote host via ssh, in 17the named repository, and stores the sent pack in the local 18repository. 19 20OPTIONS 21------- 22--exec=<git-upload-pack>:: 23 Use this to specify the path to 'git-upload-pack' on the 24 remote side, if it is not found on your $PATH. 25 Installations of sshd ignore the user's environment 26 setup scripts for login shells (e.g. .bash_profile) and 27 your privately installed git may not be found on the system 28 default $PATH. Another workaround suggested is to set 29 up your $PATH in ".bashrc", but this flag is for people 30 who do not want to pay the overhead for non-interactive 31 shells by having a lean .bashrc file (they set most of 32 the things up in .bash_profile). 33 34<host>:: 35 A remote host that houses the repository. When this 36 part is specified, 'git-upload-pack' is invoked via 37 ssh. 38 39<directory>:: 40 The repository to sync from. 41 42<head>...:: 43 The heads to update. This is relative to $GIT_DIR 44 (e.g. "HEAD", "refs/heads/master"). When unspecified, 45 all heads are updated to match the remote repository. 46+ 47Usually all the refs from existing repository are stored 48under the same name in the new repository. Giving explicit 49<head> arguments instead writes the object names and refs to 50the standard output, just like get-fetch-pack does. 51 52Author 53------ 54Written by Linus Torvalds <torvalds@osdl.org> 55 56Documentation 57-------------- 58Documentation by Junio C Hamano. 59 60 61GIT 62--- 63Part of the gitlink:git[7] suite 64