|
| 1 | +git-http-push(1) |
| 2 | +================ |
| 3 | + |
| 4 | +NAME |
| 5 | +---- |
| 6 | +git-http-push - Push missing objects using HTTP/DAV. |
| 7 | + |
| 8 | + |
| 9 | +SYNOPSIS |
| 10 | +-------- |
| 11 | +'git-http-push' [--complete] [--force] [--verbose] <url> <ref> [<ref>...] |
| 12 | + |
| 13 | +DESCRIPTION |
| 14 | +----------- |
| 15 | +Sends missing objects to remote repository, and updates the |
| 16 | +remote branch. |
| 17 | + |
| 18 | + |
| 19 | +OPTIONS |
| 20 | +------- |
| 21 | +--complete:: |
| 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 | +--verbose:: |
| 34 | + Report the list of objects being walked locally and the |
| 35 | + list of objects successfully sent to the remote repository. |
| 36 | + |
| 37 | +<ref>...: |
| 38 | + The remote refs to update. |
| 39 | + |
| 40 | + |
| 41 | +Specifying the Refs |
| 42 | +------------------- |
| 43 | + |
| 44 | +A '<ref>' specification can be either a single pattern, or a pair |
| 45 | +of such patterns separated by a colon ":" (this means that a ref name |
| 46 | +cannot have a colon in it). A single pattern '<name>' is just a |
| 47 | +shorthand for '<name>:<name>'. |
| 48 | + |
| 49 | +Each pattern pair consists of the source side (before the colon) |
| 50 | +and the destination side (after the colon). The ref to be |
| 51 | +pushed is determined by finding a match that matches the source |
| 52 | +side, and where it is pushed is determined by using the |
| 53 | +destination side. |
| 54 | + |
| 55 | + - It is an error if <src> does not match exactly one of the |
| 56 | + local refs. |
| 57 | + |
| 58 | + - If <dst> does not match any remote ref, either |
| 59 | + |
| 60 | + * it has to start with "refs/"; <dst> is used as the |
| 61 | + destination literally in this case. |
| 62 | + |
| 63 | + * <src> == <dst> and the ref that matched the <src> must not |
| 64 | + exist in the set of remote refs; the ref matched <src> |
| 65 | + locally is used as the name of the destination. |
| 66 | + |
| 67 | +Without '--force', the <src> ref is stored at the remote only if |
| 68 | +<dst> does not exist, or <dst> is a proper subset (i.e. an |
| 69 | +ancestor) of <src>. This check, known as "fast forward check", |
| 70 | +is performed in order to avoid accidentally overwriting the |
| 71 | +remote ref and lose other peoples' commits from there. |
| 72 | + |
| 73 | +With '--force', the fast forward check is disabled for all refs. |
| 74 | + |
| 75 | +Optionally, a <ref> parameter can be prefixed with a plus '+' sign |
| 76 | +to disable the fast-forward check only on that ref. |
| 77 | + |
| 78 | + |
| 79 | +Author |
| 80 | +------ |
| 81 | +Written by Nick Hengeveld <nickh@reactrix.com> |
| 82 | + |
| 83 | +Documentation |
| 84 | +-------------- |
| 85 | +Documentation by Nick Hengeveld |
| 86 | + |
| 87 | +GIT |
| 88 | +--- |
| 89 | +Part of the gitlink:git[7] suite |
0 commit comments