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