1GIT-SEND-PACK(1) Git Manual GIT-SEND-PACK(1)
2
6 git-send-pack - Push objects over git protocol to another repository
7
9 git-send-pack [--all] [--force] [--receive-pack=<git-receive-pack>]
10 [--verbose] [--thin] [<host>:]<directory> [<ref>...]
11
13 Usually you would want to use git-push(1) which is a higher level
14 wrapper of this command instead.
15 Invokes git-receive-pack on a possibly remote repository, and updates
17 it from the current repository, sending named refs.
18
20 --receive-pack=<git-receive-pack>
21 Path to the git-receive-pack program on the remote end. Sometimes
22 useful when pushing to a remote repository over ssh, and you do not
23 have the program in a directory on the default $PATH.
24 --exec=<git-receive-pack>
26 Same as --receive-pack=<git-receive-pack>.
27 --all
29 Instead of explicitly specifying which refs to update, update all
30 heads that locally exist.
31 --force
33 Usually, the command refuses to update a remote ref that is not an
34 ancestor of the local ref used to overwrite it. This flag disables
35 the check. What this means is that the remote repository can lose
36 commits; use it with care.
37 --verbose
39 Run verbosely.
40 --thin
42 Spend extra cycles to minimize the number of objects to be sent.
43 Use it on slower connection.
44 <host>
46 A remote host to house the repository. When this part is specified,
47 git-receive-pack is invoked via ssh.
48 <directory>
50 The repository to update.
51 <ref>...
53 The remote refs to update.
54
56 There are three ways to specify which refs to update on the remote end.
57 With --all flag, all refs that exist locally are transferred to the
59 remote side. You cannot specify any <ref> if you use this flag.
60 Without --all and without any <ref>, the heads that exist both on the
62 local side and on the remote side are updated.
63 When one or more <ref> are specified explicitly, it can be either a
65 single pattern, or a pair of such pattern separated by a colon ":"
66 (this means that a ref name cannot have a colon in it). A single
67 pattern <name> is just a shorthand for <name>:<name>.
68 Each pattern pair consists of the source side (before the colon) and
70 the destination side (after the colon). The ref to be pushed is
71 determined by finding a match that matches the source side, and where
72 it is pushed is determined by using the destination side.
73 · It is an error if <src> does not match exactly one of the local
76 refs.
77 · It is an error if <dst> matches more than one remote refs.
79 · If <dst> does not match any remote ref, either
81 · it has to start with "refs/"; <dst> is used as the destination
84 literally in this case.
85 · <src> == <dst> and the ref that matched the <src> must not
87 exist in the set of remote refs; the ref matched <src> locally
88 is used as the name of the destination.
89 Without --force, the <src> ref is stored at the remote only if <dst>
90 does not exist, or <dst> is a proper subset (i.e. an ancestor) of
91 <src>. This check, known as "fast forward check", is performed in order
92 to avoid accidentally overwriting the remote ref and lose other
93 peoples´ commits from there.
94 With --force, the fast forward check is disabled for all refs.
96 Optionally, a <ref> parameter can be prefixed with a plus + sign to
98 disable the fast-forward check only on that ref.
99
101 Written by Linus Torvalds <torvalds@osdl.org>
102
104 Documentation by Junio C Hamano.
105
107 Part of the git(7) suite
108Git 1.5.3.3 10/09/2007 GIT-SEND-PACK(1)