Documentation/git-send-pack.txt

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