1GIT-HTTP-PUSH(1)                  Git Manual                  GIT-HTTP-PUSH(1)
2
3
4

NAME

6       git-http-push - Push objects over HTTP/DAV to another repository
7

SYNOPSIS

9       git http-push [--all] [--dry-run] [--force] [--verbose] <url> <ref>
10       [<ref>...]
11

DESCRIPTION

13       Sends missing objects to remote repository, and updates the remote
14       branch.
15
16       NOTE: This command is temporarily disabled if your libcurl is older
17       than 7.16, as the combination has been reported not to work and
18       sometimes corrupts repository.
19

OPTIONS

21       --all
22           Do not assume that the remote repository is complete in its current
23           state, and verify all objects in the entire local ref’s history
24           exist in the remote repository.
25
26       --force
27           Usually, the command refuses to update a remote ref that is not an
28           ancestor of the local ref used to overwrite it. This flag disables
29           the check. What this means is that the remote repository can lose
30           commits; use it with care.
31
32       --dry-run
33           Do everything except actually send the updates.
34
35       --verbose
36           Report the list of objects being walked locally and the list of
37           objects successfully sent to the remote repository.
38
39       -d, -D
40           Remove <ref> from remote repository. The specified branch cannot be
41           the remote HEAD. If -d is specified the following other conditions
42           must also be met:
43
44           ·   Remote HEAD must resolve to an object that exists locally
45
46           ·   Specified branch resolves to an object that exists locally
47
48           ·   Specified branch is an ancestor of the remote HEAD
49
50       <ref>...
51           The remote refs to update.
52

SPECIFYING THE REFS

54       A <ref> specification can be either a single pattern, or a pair of such
55       patterns separated by a colon ":" (this means that a ref name cannot
56       have a colon in it). A single pattern <name> is just a shorthand for
57       <name>:<name>.
58
59       Each pattern pair consists of the source side (before the colon) and
60       the destination side (after the colon). The ref to be pushed is
61       determined by finding a match that matches the source side, and where
62       it is pushed is determined by using the destination side.
63
64       ·   It is an error if <src> does not match exactly one of the local
65           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 destination
70               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> locally
74               is used as the name of the destination.
75
76       Without --force, the <src> ref is stored at the remote only if <dst>
77       does not exist, or <dst> is a proper subset (i.e. an ancestor) of
78       <src>. This check, known as "fast-forward check", is performed in order
79       to avoid accidentally overwriting the remote ref and lose other
80       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 to
85       disable the fast-forward check only on that ref.
86

AUTHOR

88       Written by Nick Hengeveld <nickh@reactrix.com[1]>
89

DOCUMENTATION

91       Documentation by Nick Hengeveld
92

GIT

94       Part of the git(1) suite
95

NOTES

97        1. nickh@reactrix.com
98           mailto:nickh@reactrix.com
99
100
101
102Git 1.7.4.4                       04/11/2011                  GIT-HTTP-PUSH(1)
Impressum