]>
Commit | Line | Data |
---|---|---|
2a245013 JH |
1 | git-send-pack(1) |
2 | ================ | |
2a245013 JH |
3 | |
4 | NAME | |
5 | ---- | |
2de9b711 | 6 | git-send-pack - Push objects over Git protocol to another repository |
2a245013 JH |
7 | |
8 | ||
9 | SYNOPSIS | |
10 | -------- | |
7791a1d9 | 11 | [verse] |
5a277f3f | 12 | 'git send-pack' [--all] [--dry-run] [--force] [--receive-pack=<git-receive-pack>] [--verbose] [--thin] [<host>:]<directory> [<ref>...] |
2a245013 JH |
13 | |
14 | DESCRIPTION | |
15 | ----------- | |
0b444cdb | 16 | Usually you would want to use 'git push', which is a |
483bc4f0 | 17 | higher-level wrapper of this command, instead. See linkgit:git-push[1]. |
5cb545fa | 18 | |
ba020ef5 | 19 | Invokes 'git-receive-pack' on a possibly remote repository, and |
ab9b3138 | 20 | updates it from the current repository, sending named refs. |
2a245013 JH |
21 | |
22 | ||
23 | OPTIONS | |
24 | ------- | |
3240240f | 25 | --receive-pack=<git-receive-pack>:: |
ba020ef5 | 26 | Path to the 'git-receive-pack' program on the remote |
2a245013 JH |
27 | end. Sometimes useful when pushing to a remote |
28 | repository over ssh, and you do not have the program in | |
29 | a directory on the default $PATH. | |
30 | ||
3240240f | 31 | --exec=<git-receive-pack>:: |
d23842fd UKK |
32 | Same as \--receive-pack=<git-receive-pack>. |
33 | ||
3240240f | 34 | --all:: |
9553d20b | 35 | Instead of explicitly specifying which refs to update, |
5c633a4c | 36 | update all heads that locally exist. |
9553d20b | 37 | |
26be19ba JK |
38 | --stdin:: |
39 | Take the list of refs from stdin, one per line. If there | |
40 | are refs specified on the command line in addition to this | |
41 | option, then the refs from stdin are processed after those | |
42 | on the command line. | |
43 | + | |
44 | If '--stateless-rpc' is specified together with this option then | |
45 | the list of refs must be in packet format (pkt-line). Each ref must | |
46 | be in a separate packet, and the list must end with a flush packet. | |
47 | ||
3240240f | 48 | --dry-run:: |
a63103ae BE |
49 | Do everything except actually send the updates. |
50 | ||
3240240f | 51 | --force:: |
ab9b3138 JH |
52 | Usually, the command refuses to update a remote ref that |
53 | is not an ancestor of the local ref used to overwrite it. | |
54 | This flag disables the check. What this means is that | |
55 | the remote repository can lose commits; use it with | |
56 | care. | |
57 | ||
3240240f | 58 | --verbose:: |
18bd8821 UKK |
59 | Run verbosely. |
60 | ||
3240240f | 61 | --thin:: |
738820a9 SB |
62 | Send a "thin" pack, which records objects in deltified form based |
63 | on objects not included in the pack to reduce network traffic. | |
18bd8821 | 64 | |
2a245013 JH |
65 | <host>:: |
66 | A remote host to house the repository. When this | |
ba020ef5 | 67 | part is specified, 'git-receive-pack' is invoked via |
2a245013 JH |
68 | ssh. |
69 | ||
70 | <directory>:: | |
71 | The repository to update. | |
72 | ||
23bed43d | 73 | <ref>...:: |
9553d20b JH |
74 | The remote refs to update. |
75 | ||
76 | ||
77 | Specifying the Refs | |
78 | ------------------- | |
79 | ||
80 | There are three ways to specify which refs to update on the | |
81 | remote end. | |
82 | ||
abda1ef5 | 83 | With '--all' flag, all refs that exist locally are transferred to |
ab9b3138 | 84 | the remote side. You cannot specify any '<ref>' if you use |
9553d20b JH |
85 | this flag. |
86 | ||
5c633a4c | 87 | Without '--all' and without any '<ref>', the heads that exist |
9553d20b JH |
88 | both on the local side and on the remote side are updated. |
89 | ||
26be19ba JK |
90 | When one or more '<ref>' are specified explicitly (whether on the |
91 | command line or via `--stdin`), it can be either a | |
9553d20b | 92 | single pattern, or a pair of such pattern separated by a colon |
df8baa42 | 93 | ":" (this means that a ref name cannot have a colon in it). A |
9553d20b | 94 | single pattern '<name>' is just a shorthand for '<name>:<name>'. |
ab9b3138 | 95 | |
9553d20b | 96 | Each pattern pair consists of the source side (before the colon) |
ab9b3138 | 97 | and the destination side (after the colon). The ref to be |
9553d20b JH |
98 | pushed is determined by finding a match that matches the source |
99 | side, and where it is pushed is determined by using the | |
ae36bdcf | 100 | destination side. The rules used to match a ref are the same |
0b444cdb | 101 | rules used by 'git rev-parse' to resolve a symbolic ref |
483bc4f0 | 102 | name. See linkgit:git-rev-parse[1]. |
9553d20b | 103 | |
ab9b3138 JH |
104 | - It is an error if <src> does not match exactly one of the |
105 | local refs. | |
9553d20b JH |
106 | |
107 | - It is an error if <dst> matches more than one remote refs. | |
108 | ||
109 | - If <dst> does not match any remote ref, either | |
110 | ||
df8baa42 | 111 | * it has to start with "refs/"; <dst> is used as the |
9553d20b JH |
112 | destination literally in this case. |
113 | ||
df8baa42 | 114 | * <src> == <dst> and the ref that matched the <src> must not |
9553d20b JH |
115 | exist in the set of remote refs; the ref matched <src> |
116 | locally is used as the name of the destination. | |
117 | ||
ab9b3138 JH |
118 | Without '--force', the <src> ref is stored at the remote only if |
119 | <dst> does not exist, or <dst> is a proper subset (i.e. an | |
a75d7b54 | 120 | ancestor) of <src>. This check, known as "fast-forward check", |
ab9b3138 JH |
121 | is performed in order to avoid accidentally overwriting the |
122 | remote ref and lose other peoples' commits from there. | |
123 | ||
a75d7b54 | 124 | With '--force', the fast-forward check is disabled for all refs. |
ab9b3138 JH |
125 | |
126 | Optionally, a <ref> parameter can be prefixed with a plus '+' sign | |
127 | to disable the fast-forward check only on that ref. | |
128 | ||
2a245013 JH |
129 | GIT |
130 | --- | |
9e1f0a85 | 131 | Part of the linkgit:git[1] suite |