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>] [--quiet] [--verbose] [--thin] [<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--dry-run:: 39 Do everything except actually send the updates. 40 41--force:: 42 Usually, the command refuses to update a remote ref that 43 is not an ancestor of the local ref used to overwrite it. 44 This flag disables the check. What this means is that 45 the remote repository can lose commits; use it with 46 care. 47 48--quiet:: 49 Print only error messages. 50 51--verbose:: 52 Run verbosely. 53 54--thin:: 55 Send a "thin" pack, which records objects in deltified form based 56 on objects not included in the pack to reduce network traffic. 57 58<host>:: 59 A remote host to house the repository. When this 60 part is specified, 'git-receive-pack' is invoked via 61 ssh. 62 63<directory>:: 64 The repository to update. 65 66<ref>...:: 67 The remote refs to update. 68 69 70Specifying the Refs 71------------------- 72 73There are three ways to specify which refs to update on the 74remote end. 75 76With '--all' flag, all refs that exist locally are transferred to 77the remote side. You cannot specify any '<ref>' if you use 78this flag. 79 80Without '--all' and without any '<ref>', the heads that exist 81both on the local side and on the remote side are updated. 82 83When one or more '<ref>' are specified explicitly, it can be either a 84single pattern, or a pair of such pattern separated by a colon 85":" (this means that a ref name cannot have a colon in it). A 86single pattern '<name>' is just a shorthand for '<name>:<name>'. 87 88Each pattern pair consists of the source side (before the colon) 89and the destination side (after the colon). The ref to be 90pushed is determined by finding a match that matches the source 91side, and where it is pushed is determined by using the 92destination side. The rules used to match a ref are the same 93rules used by 'git rev-parse' to resolve a symbolic ref 94name. See linkgit:git-rev-parse[1]. 95 96 - It is an error if <src> does not match exactly one of the 97 local refs. 98 99 - It is an error if <dst> matches more than one remote refs. 100 101 - If <dst> does not match any remote ref, either 102 103 * it has to start with "refs/"; <dst> is used as the 104 destination literally in this case. 105 106 * <src> == <dst> and the ref that matched the <src> must not 107 exist in the set of remote refs; the ref matched <src> 108 locally is used as the name of the destination. 109 110Without '--force', the <src> ref is stored at the remote only if 111<dst> does not exist, or <dst> is a proper subset (i.e. an 112ancestor) of <src>. This check, known as "fast-forward check", 113is performed in order to avoid accidentally overwriting the 114remote ref and lose other peoples' commits from there. 115 116With '--force', the fast-forward check is disabled for all refs. 117 118Optionally, a <ref> parameter can be prefixed with a plus '+' sign 119to disable the fast-forward check only on that ref. 120 121GIT 122--- 123Part of the linkgit:git[1] suite