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