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