--- /dev/null
+<?xml version="1.0" encoding="UTF-8"?>\r
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">\r
+\r
+<article lang="en" id="git-http-push(1)">\r
+<articleinfo>\r
+ <title>git-http-push(1)</title>\r
+ <indexterm>\r
+ <primary>git-http-push(1)</primary>\r
+ </indexterm>\r
+</articleinfo>\r
+<simplesect id="_name">\r
+<title>NAME</title>\r
+<simpara>git-http-push - Push objects over HTTP/DAV to another repository</simpara>\r
+</simplesect>\r
+<simplesect id="_synopsis">\r
+<title>SYNOPSIS</title>\r
+<simpara><emphasis>git http-push</emphasis> [--all] [--dry-run] [--force] [--verbose] <url> <ref> [<ref>…]</simpara>\r
+</simplesect>\r
+<simplesect id="_description">\r
+<title>DESCRIPTION</title>\r
+<simpara>Sends missing objects to remote repository, and updates the\r
+remote branch.</simpara>\r
+<simpara><emphasis role="strong">NOTE</emphasis>: This command is temporarily disabled if your libcurl\r
+is older than 7.16, as the combination has been reported\r
+not to work and sometimes corrupts repository.</simpara>\r
+</simplesect>\r
+<simplesect id="_options">\r
+<title>OPTIONS</title>\r
+<variablelist>\r
+<varlistentry>\r
+<term>\r
+--all\r
+</term>\r
+<listitem>\r
+<simpara>\r
+ Do not assume that the remote repository is complete in its\r
+ current state, and verify all objects in the entire local\r
+ ref’s history exist in the remote repository.\r
+</simpara>\r
+</listitem>\r
+</varlistentry>\r
+<varlistentry>\r
+<term>\r
+--force\r
+</term>\r
+<listitem>\r
+<simpara>\r
+ Usually, the command refuses to update a remote ref that\r
+ is not an ancestor of the local ref used to overwrite it.\r
+ This flag disables the check. What this means is that\r
+ the remote repository can lose commits; use it with\r
+ care.\r
+</simpara>\r
+</listitem>\r
+</varlistentry>\r
+<varlistentry>\r
+<term>\r
+--dry-run\r
+</term>\r
+<listitem>\r
+<simpara>\r
+ Do everything except actually send the updates.\r
+</simpara>\r
+</listitem>\r
+</varlistentry>\r
+<varlistentry>\r
+<term>\r
+--verbose\r
+</term>\r
+<listitem>\r
+<simpara>\r
+ Report the list of objects being walked locally and the\r
+ list of objects successfully sent to the remote repository.\r
+</simpara>\r
+</listitem>\r
+</varlistentry>\r
+<varlistentry>\r
+<term>\r
+-d\r
+</term>\r
+<term>\r
+-D\r
+</term>\r
+<listitem>\r
+<simpara>\r
+ Remove <ref> from remote repository. The specified branch\r
+ cannot be the remote HEAD. If -d is specified the following\r
+ other conditions must also be met:\r
+</simpara>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+Remote HEAD must resolve to an object that exists locally\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Specified branch resolves to an object that exists locally\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+Specified branch is an ancestor of the remote HEAD\r
+</simpara>\r
+</listitem>\r
+</itemizedlist>\r
+</listitem>\r
+</varlistentry>\r
+<varlistentry>\r
+<term>\r
+<ref>…\r
+</term>\r
+<listitem>\r
+<simpara>\r
+ The remote refs to update.\r
+</simpara>\r
+</listitem>\r
+</varlistentry>\r
+</variablelist>\r
+</simplesect>\r
+<simplesect id="_specifying_the_refs">\r
+<title>Specifying the Refs</title>\r
+<simpara>A <emphasis><ref></emphasis> specification can be either a single pattern, or a pair\r
+of such patterns separated by a colon ":" (this means that a ref name\r
+cannot have a colon in it). A single pattern <emphasis><name></emphasis> is just a\r
+shorthand for <emphasis><name>:<name></emphasis>.</simpara>\r
+<simpara>Each pattern pair consists of the source side (before the colon)\r
+and the destination side (after the colon). The ref to be\r
+pushed is determined by finding a match that matches the source\r
+side, and where it is pushed is determined by using the\r
+destination side.</simpara>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+It is an error if <src> does not match exactly one of the\r
+ local refs.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+If <dst> does not match any remote ref, either\r
+</simpara>\r
+<itemizedlist>\r
+<listitem>\r
+<simpara>\r
+it has to start with "refs/"; <dst> is used as the\r
+ destination literally in this case.\r
+</simpara>\r
+</listitem>\r
+<listitem>\r
+<simpara>\r
+<src> == <dst> and the ref that matched the <src> must not\r
+ exist in the set of remote refs; the ref matched <src>\r
+ locally is used as the name of the destination.\r
+</simpara>\r
+</listitem>\r
+</itemizedlist>\r
+</listitem>\r
+</itemizedlist>\r
+<simpara>Without <emphasis>--force</emphasis>, the <src> ref is stored at the remote only if\r
+<dst> does not exist, or <dst> is a proper subset (i.e. an\r
+ancestor) of <src>. This check, known as "fast forward check",\r
+is performed in order to avoid accidentally overwriting the\r
+remote ref and lose other peoples' commits from there.</simpara>\r
+<simpara>With <emphasis>--force</emphasis>, the fast forward check is disabled for all refs.</simpara>\r
+<simpara>Optionally, a <ref> parameter can be prefixed with a plus <emphasis>+</emphasis> sign\r
+to disable the fast-forward check only on that ref.</simpara>\r
+</simplesect>\r
+<simplesect id="_author">\r
+<title>Author</title>\r
+<simpara>Written by Nick Hengeveld <<ulink url="mailto:nickh@reactrix.com">nickh@reactrix.com</ulink>></simpara>\r
+</simplesect>\r
+<simplesect id="_documentation">\r
+<title>Documentation</title>\r
+<simpara>Documentation by Nick Hengeveld</simpara>\r
+</simplesect>\r
+<simplesect id="_git">\r
+<title>GIT</title>\r
+<simpara>Part of the <xref linkend="git(1)"/> suite</simpara>\r
+</simplesect>\r
+</article>\r
OSDN Git Service
