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] [--dry-run] [--force] [--receive-pack=<git-receive-pack>] [--verbose] [--thin] [<host>:]<directory> [<ref>...]
10
13 Usually you would want to use git push, which is a higher-level wrapper
14 of this command, instead. See git-push(1).
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 --dry-run
33 Do everything except actually send the updates.
34 --force
36 Usually, the command refuses to update a remote ref that is not an
37 ancestor of the local ref used to overwrite it. This flag disables
38 the check. What this means is that the remote repository can lose
39 commits; use it with care.
40 --verbose
42 Run verbosely.
43 --thin
45 Send a "thin" pack, which records objects in deltified form based
46 on objects not included in the pack to reduce network traffic.
47 <host>
49 A remote host to house the repository. When this part is specified,
50 git-receive-pack is invoked via ssh.
51 <directory>
53 The repository to update.
54 <ref>...
56 The remote refs to update.
57
59 There are three ways to specify which refs to update on the remote end.
60 With --all flag, all refs that exist locally are transferred to the
62 remote side. You cannot specify any <ref> if you use this flag.
63 Without --all and without any <ref>, the heads that exist both on the
65 local side and on the remote side are updated.
66 When one or more <ref> are specified explicitly, it can be either a
68 single pattern, or a pair of such pattern separated by a colon ":"
69 (this means that a ref name cannot have a colon in it). A single
70 pattern <name> is just a shorthand for <name>:<name>.
71 Each pattern pair consists of the source side (before the colon) and
73 the destination side (after the colon). The ref to be pushed is
74 determined by finding a match that matches the source side, and where
75 it is pushed is determined by using the destination side. The rules
76 used to match a ref are the same rules used by git rev-parse to resolve
77 a symbolic ref name. See git-rev-parse(1).
78 · It is an error if <src> does not match exactly one of the local
80 refs.
81 · It is an error if <dst> matches more than one remote refs.
83 · If <dst> does not match any remote ref, either
85 · it has to start with "refs/"; <dst> is used as the destination
87 literally in this case.
88 · <src> == <dst> and the ref that matched the <src> must not
90 exist in the set of remote refs; the ref matched <src> locally
91 is used as the name of the destination.
92 Without --force, the <src> ref is stored at the remote only if <dst>
94 does not exist, or <dst> is a proper subset (i.e. an ancestor) of
95 <src>. This check, known as "fast-forward check", is performed in order
96 to avoid accidentally overwriting the remote ref and lose other
97 peoples' commits from there.
98 With --force, the fast-forward check is disabled for all refs.
100 Optionally, a <ref> parameter can be prefixed with a plus + sign to
102 disable the fast-forward check only on that ref.
103
105 Part of the git(1) suite
106Git 1.8.3.1 11/19/2018 GIT-SEND-PACK(1)