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