[thirdparty/git.git] / Documentation / git-http-push.txt

git-http-push(1)
================

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


SYNOPSIS
--------
'git-http-push' [--all] [--dry-run] [--force] [--verbose] <url> <ref> [<ref>...]

DESCRIPTION
-----------
Sends missing objects to remote repository, and updates the
remote branch.


OPTIONS
-------
--all::
	Do not assume that the remote repository is complete in its
	current state, and verify all objects in the entire local
	ref's history exist in the remote repository.

--force::
	Usually, the command refuses to update a remote ref that
	is not an ancestor of the local ref used to overwrite it.
	This flag disables the check.  What this means is that
	the remote repository can lose commits; use it with
	care.

--dry-run::
	Do everything except actually send the updates.

--verbose::
	Report the list of objects being walked locally and the
	list of objects successfully sent to the remote repository.

-d, -D::
	Remove <ref> from remote repository.  The specified branch
	cannot be the remote HEAD.  If -d is specified the following
	other conditions must also be met:

	- Remote HEAD must resolve to an object that exists locally
	- Specified branch resolves to an object that exists locally
	- Specified branch is an ancestor of the remote HEAD

<ref>...::
	The remote refs to update.


Specifying the Refs
-------------------

A '<ref>' specification can be either a single pattern, or a pair
of such patterns separated by a colon ":" (this means that a ref name
cannot have a colon in it).  A single pattern '<name>' is just a
shorthand for '<name>:<name>'.

Each pattern pair consists of the source side (before the colon)
and the destination side (after the colon).  The ref to be
pushed is determined by finding a match that matches the source
side, and where it is pushed is determined by using the
destination side.

 - It is an error if <src> does not match exactly one of the
   local refs.

 - If <dst> does not match any remote ref, either

   * it has to start with "refs/"; <dst> is used as the
     destination literally in this case.

   * <src> == <dst> and the ref that matched the <src> must not
     exist in the set of remote refs; the ref matched <src>
     locally is used as the name of the destination.

Without '--force', the <src> ref is stored at the remote only if
<dst> does not exist, or <dst> is a proper subset (i.e. an
ancestor) of <src>.  This check, known as "fast forward check",
is performed in order to avoid accidentally overwriting the
remote ref and lose other peoples' commits from there.

With '--force', the fast forward check is disabled for all refs.

Optionally, a <ref> parameter can be prefixed with a plus '+' sign
to disable the fast-forward check only on that ref.


Author
------
Written by Nick Hengeveld <nickh@reactrix.com>

Documentation
--------------
Documentation by Nick Hengeveld

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