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