1git-http-push(1) 2================ 3 4NAME 5---- 6git-http-push - Push objects over HTTP/DAV to another repository 7 8 9SYNOPSIS 10-------- 11[verse] 12'git http-push' [--all] [--dry-run] [--force] [--verbose] <url> <ref> [<ref>...] 13 14DESCRIPTION 15----------- 16Sends missing objects to remote repository, and updates the 17remote branch. 18 19*NOTE*: This command is temporarily disabled if your libcurl 20is older than 7.16, as the combination has been reported 21not to work and sometimes corrupts repository. 22 23OPTIONS 24------- 25--all:: 26 Do not assume that the remote repository is complete in its 27 current state, and verify all objects in the entire local 28 ref's history exist in the remote repository. 29 30--force:: 31 Usually, the command refuses to update a remote ref that 32 is not an ancestor of the local ref used to overwrite it. 33 This flag disables the check. What this means is that 34 the remote repository can lose commits; use it with 35 care. 36 37--dry-run:: 38 Do everything except actually send the updates. 39 40--verbose:: 41 Report the list of objects being walked locally and the 42 list of objects successfully sent to the remote repository. 43 44-d:: 45-D:: 46 Remove <ref> from remote repository. The specified branch 47 cannot be the remote HEAD. If -d is specified the following 48 other conditions must also be met: 49 50 - Remote HEAD must resolve to an object that exists locally 51 - Specified branch resolves to an object that exists locally 52 - Specified branch is an ancestor of the remote HEAD 53 54<ref>...:: 55 The remote refs to update. 56 57 58Specifying the Refs 59------------------- 60 61A '<ref>' specification can be either a single pattern, or a pair 62of such patterns separated by a colon ":" (this means that a ref name 63cannot have a colon in it). A single pattern '<name>' is just a 64shorthand for '<name>:<name>'. 65 66Each pattern pair consists of the source side (before the colon) 67and the destination side (after the colon). The ref to be 68pushed is determined by finding a match that matches the source 69side, and where it is pushed is determined by using the 70destination side. 71 72 - It is an error if <src> does not match exactly one of the 73 local refs. 74 75 - If <dst> does not match any remote ref, either 76 77 * it has to start with "refs/"; <dst> is used as the 78 destination literally in this case. 79 80 * <src> == <dst> and the ref that matched the <src> must not 81 exist in the set of remote refs; the ref matched <src> 82 locally is used as the name of the destination. 83 84Without `--force`, the <src> ref is stored at the remote only if 85<dst> does not exist, or <dst> is a proper subset (i.e. an 86ancestor) of <src>. This check, known as "fast-forward check", 87is performed in order to avoid accidentally overwriting the 88remote ref and lose other peoples' commits from there. 89 90With `--force`, the fast-forward check is disabled for all refs. 91 92Optionally, a <ref> parameter can be prefixed with a plus '+' sign 93to disable the fast-forward check only on that ref. 94 95GIT 96--- 97Part of the linkgit:git[1] suite