[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.

*NOTE*: This command is temporarily disabled if your libcurl
is older than 7.16, as the combination has been reported
not to work and sometimes corrupts repository.

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.

GIT
---
Part of the linkgit:git[1] 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	--------
b1889c36	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
8da1e212 JH	18	NOTE: This command is temporarily disabled if your libcurl
8da1e212 JH	19	is older than 7.16, as the combination has been reported
4f5f998f	20	not to work and sometimes corrupts repository.
58e60dd2 NH	21
	22	OPTIONS
	23	-------
d8190a8e	24	--all::
58e60dd2 NH	25	Do not assume that the remote repository is complete in its
	26	current state, and verify all objects in the entire local
	27	ref's history exist in the remote repository.
	28
	29	--force::
	30	Usually, the command refuses to update a remote ref that
	31	is not an ancestor of the local ref used to overwrite it.
	32	This flag disables the check. What this means is that
	33	the remote repository can lose commits; use it with
	34	care.
	35
fe5d1d3e SP	36	--dry-run::
	37	Do everything except actually send the updates.
	38
58e60dd2 NH	39	--verbose::
	40	Report the list of objects being walked locally and the
	41	list of objects successfully sent to the remote repository.
	42
3240240f SB	43	-d::
3240240f SB	44	-D::
d8190a8e AR	45	Remove <ref> from remote repository. The specified branch
	46	cannot be the remote HEAD. If -d is specified the following
	47	other conditions must also be met:
	48
	49	- Remote HEAD must resolve to an object that exists locally
	50	- Specified branch resolves to an object that exists locally
	51	- Specified branch is an ancestor of the remote HEAD
	52
23bed43d	53	<ref>...::
58e60dd2 NH	54	The remote refs to update.
	55
	56
	57	Specifying the Refs
	58	-------------------
	59
	60	A '<ref>' specification can be either a single pattern, or a pair
	61	of such patterns separated by a colon ":" (this means that a ref name
a6080a0a	62	cannot have a colon in it). A single pattern '<name>' is just a
58e60dd2 NH	63	shorthand for '<name>:<name>'.
	64
	65	Each pattern pair consists of the source side (before the colon)
	66	and the destination side (after the colon). The ref to be
	67	pushed is determined by finding a match that matches the source
	68	side, and where it is pushed is determined by using the
	69	destination side.
	70
	71	- It is an error if <src> does not match exactly one of the
	72	local refs.
	73
	74	- If <dst> does not match any remote ref, either
	75
	76	* it has to start with "refs/"; <dst> is used as the
	77	destination literally in this case.
	78
	79	* <src> == <dst> and the ref that matched the <src> must not
	80	exist in the set of remote refs; the ref matched <src>
	81	locally is used as the name of the destination.
	82
	83	Without '--force', the <src> ref is stored at the remote only if
	84	<dst> does not exist, or <dst> is a proper subset (i.e. an
a75d7b54	85	ancestor) of <src>. This check, known as "fast-forward check",
58e60dd2 NH	86	is performed in order to avoid accidentally overwriting the
	87	remote ref and lose other peoples' commits from there.
	88
a75d7b54	89	With '--force', the fast-forward check is disabled for all refs.
58e60dd2 NH	90
	91	Optionally, a <ref> parameter can be prefixed with a plus '+' sign
	92	to disable the fast-forward check only on that ref.
	93
58e60dd2 NH	94	GIT
58e60dd2 NH	95	---
9e1f0a85	96	Part of the linkgit:git[1] suite