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] [--force] [--verbose] <url> <ref> [<ref>...]
10

DESCRIPTION

12       Sends missing objects to remote repository, and updates the remote
13       branch.
14

OPTIONS

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

SPECIFYING THE REFS

47       A <ref> specification can be either a single pattern, or a pair of such
48       patterns separated by a colon ":" (this means that a ref name cannot
49       have a colon in it). A single pattern <name> is just a shorthand for
50       <name>:<name>.
51
52       Each pattern pair consists of the source side (before the colon) and
53       the destination side (after the colon). The ref to be pushed is
54       determined by finding a match that matches the source side, and where
55       it is pushed is determined by using the destination side.
56
57
58       ·   It is an error if <src> does not match exactly one of the local
59           refs.
60
61       ·   If <dst> does not match any remote ref, either
62
63
64           ·   it has to start with "refs/"; <dst> is used as the destination
65               literally in this case.
66
67           ·   <src> == <dst> and the ref that matched the <src> must not
68               exist in the set of remote refs; the ref matched <src> locally
69               is used as the name of the destination.
70       Without --force, the <src> ref is stored at the remote only if <dst>
71       does not exist, or <dst> is a proper subset (i.e. an ancestor) of
72       <src>. This check, known as "fast forward check", is performed in order
73       to avoid accidentally overwriting the remote ref and lose other
74       peoples´ commits from there.
75
76       With --force, the fast forward check is disabled for all refs.
77
78       Optionally, a <ref> parameter can be prefixed with a plus + sign to
79       disable the fast-forward check only on that ref.
80

AUTHOR

82       Written by Nick Hengeveld <nickh@reactrix.com>
83

DOCUMENTATION

85       Documentation by Nick Hengeveld
86

GIT

88       Part of the git(7) suite
89
90
91
92
93Git 1.5.3.3                       10/09/2007                  GIT-HTTP-PUSH(1)