]>
Commit | Line | Data |
---|---|---|
8b3d9dc0 JH |
1 | git-fetch-pack(1) |
2 | ================= | |
3 | v0.1, July 2005 | |
4 | ||
5 | NAME | |
6 | ---- | |
7 | git-fetch-pack - Receive missing objects from another repository. | |
8 | ||
9 | ||
10 | SYNOPSIS | |
11 | -------- | |
12 | git-fetch-pack [-q] [--exec=<git-upload-pack>] [<host>:]<directory> [<head>...] < <commit-list> | |
13 | ||
14 | DESCRIPTION | |
15 | ----------- | |
16 | Invokes 'git-upload-pack' on a potentially remote repository, | |
17 | and asks it to send objects missing from this repository, to | |
18 | update the named heads. The list of commits available locally | |
19 | is fed from the standard input, to be sent to 'git-upload-pack' | |
20 | running on the other end. | |
21 | ||
22 | This command can be used only when the local side has a common | |
23 | (ancestor) commit with the remote head that is being pulled | |
24 | from. Use 'git-clone-pack' for that. | |
25 | ||
26 | ||
27 | OPTIONS | |
28 | ------- | |
29 | -q:: | |
30 | Pass '-q' flag to 'git-unpack-objects'; this makes the | |
31 | cloning process less verbose. | |
32 | ||
33 | --exec=<git-upload-pack>:: | |
34 | Use this to specify the path to 'git-upload-pack' on the | |
35 | remote side, if is not found on your $PATH. | |
36 | Installations of sshd ignores the user's environment | |
37 | setup scripts for login shells (e.g. .bash_profile) and | |
38 | your privately installed GIT may not be found on the system | |
39 | default $PATH. Another workaround suggested is to set | |
40 | up your $PATH in ".bashrc", but this flag is for people | |
41 | who do not want to pay the overhead for non-interactive | |
42 | shells by having a lean .bashrc file (they set most of | |
43 | the things up in .bash_profile). | |
44 | ||
45 | <host>:: | |
46 | A remote host that houses the repository. When this | |
47 | part is specified, 'git-upload-pack' is invoked via | |
48 | ssh. | |
49 | ||
50 | <directory>:: | |
51 | The repository to sync from. | |
52 | ||
53 | <head>...:: | |
54 | The remote heads to update from. This is relative to | |
55 | $GIT_DIR (e.g. "HEAD", "refs/heads/master"). When | |
56 | unspecified, update from all heads the remote side has. | |
57 | ||
58 | However the program refuses to work if more than one | |
59 | remote head matches the specified heads. I am not sure | |
60 | what this means... Help!!!!! | |
61 | ||
62 | ||
63 | Author | |
64 | ------ | |
65 | Written by Linus Torvalds <torvalds@osdl.org> | |
66 | ||
67 | Documentation | |
68 | -------------- | |
69 | Documentation by Junio C Hamano. | |
70 | ||
71 | GIT | |
72 | --- | |
73 | Part of the link:git.html[git] suite |