diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2008-07-06 05:20:31 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2008-07-06 05:20:31 +0000 |
| commit | ba4b9286c25f18c7ebbb809ee5732a7810377ab6 (patch) | |
| tree | 390507328a7564b65dc803683c34235700b97409 /git-push.html | |
| parent | 05bf9c54a827e48b2b576488f5170a3490b5180e (diff) | |
| download | git-htmldocs-ba4b9286c25f18c7ebbb809ee5732a7810377ab6.tar.gz | |
Autogenerated HTML docs for v1.5.6.2-212-g08b5
Diffstat (limited to 'git-push.html')
| -rw-r--r-- | git-push.html | 230 |
1 files changed, 139 insertions, 91 deletions
diff --git a/git-push.html b/git-push.html index 4697ad8f5..c08ddb54d 100644 --- a/git-push.html +++ b/git-push.html @@ -3,7 +3,7 @@ <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 7.0.2" />
+<meta name="generator" content="AsciiDoc 8.2.5" />
<style type="text/css">
/* Debug borders */
p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
@@ -16,8 +16,13 @@ body { margin: 1em 5% 1em 5%;
}
-a { color: blue; }
-a:visited { color: fuchsia; }
+a {
+ color: blue;
+ text-decoration: underline;
+}
+a:visited {
+ color: fuchsia;
+}
em {
font-style: italic;
@@ -39,13 +44,18 @@ h1, h2, h3, h4, h5, h6 { line-height: 1.3;
}
-h1 {
+h1, h2, h3 {
border-bottom: 2px solid silver;
}
h2 {
- border-bottom: 2px solid silver;
padding-top: 0.5em;
}
+h3 {
+ float: left;
+}
+h3 + * {
+ clear: left;
+}
div.sectionbody {
font-family: serif;
@@ -70,7 +80,7 @@ span#author { color: #527bbd;
font-family: sans-serif;
font-weight: bold;
- font-size: 1.2em;
+ font-size: 1.1em;
}
span#email {
}
@@ -139,6 +149,9 @@ div.sidebarblock > div.content { padding: 0.5em;
}
+div.listingblock {
+ margin-right: 0%;
+}
div.listingblock > div.content {
border: 1px solid silver;
background: #f4f4f4;
@@ -148,9 +161,13 @@ div.listingblock > div.content { div.quoteblock > div.content {
padding-left: 2.0em;
}
-div.quoteblock .attribution {
+
+div.attribution {
text-align: right;
}
+div.verseblock + div.attribution {
+ text-align: left;
+}
div.admonitionblock .icon {
vertical-align: top;
@@ -194,13 +211,12 @@ dd > *:first-child { ul, ol {
list-style-position: outside;
}
-ol.olist2 {
+div.olist2 ol {
list-style-type: lower-alpha;
}
div.tableblock > table {
- border-color: #527bbd;
- border-width: 3px;
+ border: 3px solid #527bbd;
}
thead {
font-family: sans-serif;
@@ -214,6 +230,9 @@ div.hlist { margin-top: 0.8em;
margin-bottom: 0.8em;
}
+div.hlist td {
+ padding-bottom: 5px;
+}
td.hlist1 {
vertical-align: top;
font-style: italic;
@@ -226,7 +245,33 @@ td.hlist2 { @media print {
div#footer-badges { display: none; }
}
-include::./stylesheets/xhtml11-manpage.css[]
+
+div#toctitle {
+ color: #527bbd;
+ font-family: sans-serif;
+ font-size: 1.1em;
+ font-weight: bold;
+ margin-top: 1.0em;
+ margin-bottom: 0.1em;
+}
+
+div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
+ margin-top: 0;
+ margin-bottom: 0;
+}
+div.toclevel2 {
+ margin-left: 2em;
+ font-size: 0.9em;
+}
+div.toclevel3 {
+ margin-left: 4em;
+ font-size: 0.9em;
+}
+div.toclevel4 {
+ margin-left: 6em;
+ font-size: 0.9em;
+}
+include1::./stylesheets/xhtml11-manpage.css[]
/* Workarounds for IE6's broken and incomplete CSS2. */
div.sidebar-content {
@@ -255,6 +300,9 @@ div.exampleblock-content { border-left: 2px solid silver;
padding-left: 0.5em;
}
+
+/* IE6 sets dynamically generated links as visited. */
+div#toc a:visited { color: blue; }
</style>
<title>git-push(1)</title>
</head>
@@ -276,17 +324,17 @@ git-push(1) Manual Page <div class="content"><em>git push</em> [--all] [--dry-run] [--tags] [--receive-pack=<git-receive-pack>]
[--repo=all] [-f | --force] [-v | --verbose] [<repository> <refspec>…]</div></div>
</div>
-<h2>DESCRIPTION</h2>
+<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
-<p>Updates remote refs using local refs, while sending objects
-necessary to complete the given refs.</p>
-<p>You can make interesting things happen to a repository
+<div class="para"><p>Updates remote refs using local refs, while sending objects
+necessary to complete the given refs.</p></div>
+<div class="para"><p>You can make interesting things happen to a repository
every time you push into it, by setting up <em>hooks</em> there. See
-documentation for <a href="git-receive-pack.html">git-receive-pack(1)</a>.</p>
+documentation for <a href="git-receive-pack.html">git-receive-pack(1)</a>.</p></div>
</div>
-<h2>OPTIONS</h2>
+<h2 id="_options">OPTIONS</h2>
<div class="sectionbody">
-<dl>
+<div class="vlist"><dl>
<dt>
<repository>
</dt>
@@ -302,30 +350,30 @@ documentation for <a href="git-receive-pack.html">git-receive-pack(1)</a>.</p> <dd>
<p>
The canonical format of a <refspec> parameter is
- <tt>+?<src>:<dst></tt>; that is, an optional plus <tt>+</tt>, followed
+ <tt><tt>?<src>:<dst></tt>; that is, an optional plus <tt></tt></tt>, followed
by the source ref, followed by a colon <tt>:</tt>, followed by
the destination ref.
</p>
-<p>The <src> side represents the source branch (or arbitrary
+<div class="para"><p>The <src> side represents the source branch (or arbitrary
"SHA1 expression", such as <tt>master~4</tt> (four parents before the
tip of <tt>master</tt> branch); see <a href="git-rev-parse.html">git-rev-parse(1)</a>) that you
-want to push. The <dst> side represents the destination location.</p>
-<p>The local ref that matches <src> is used
+want to push. The <dst> side represents the destination location.</p></div>
+<div class="para"><p>The local ref that matches <src> is used
to fast forward the remote ref that matches <dst> (or, if no <dst> was
specified, the same ref that <src> referred to locally). If
the optional leading plus <tt>+</tt> is used, the remote ref is updated
-even if it does not result in a fast forward update.</p>
-<p><tt>tag <tag></tt> means the same as <tt>refs/tags/<tag>:refs/tags/<tag></tt>.</p>
-<p>A parameter <ref> without a colon pushes the <ref> from the source
-repository to the destination repository under the same name.</p>
-<p>Pushing an empty <src> allows you to delete the <dst> ref from
-the remote repository.</p>
-<p>The special refspec <tt>:</tt> (or <tt>+:</tt> to allow non-fast forward updates)
+even if it does not result in a fast forward update.</p></div>
+<div class="para"><p><tt>tag <tag></tt> means the same as <tt>refs/tags/<tag>:refs/tags/<tag></tt>.</p></div>
+<div class="para"><p>A parameter <ref> without a colon pushes the <ref> from the source
+repository to the destination repository under the same name.</p></div>
+<div class="para"><p>Pushing an empty <src> allows you to delete the <dst> ref from
+the remote repository.</p></div>
+<div class="para"><p>The special refspec <tt>:</tt> (or <tt>+:</tt> to allow non-fast forward updates)
directs git to push "matching" heads: for every head that exists on
the local side, the remote side is updated if a head of the same name
already exists on the remote side. This is the default operation mode
if no explicit refspec is found (that is neither on the command line
-nor in any Push line of the corresponding remotes file---see below).</p>
+nor in any Push line of the corresponding remotes file---see below).</p></div>
</dd>
<dt>
--all
@@ -375,7 +423,7 @@ nor in any Push line of the corresponding remotes file---see below).</p> </dt>
<dd>
<p>
- Path to the <tt>git-receive-pack</tt> program on the remote
+ Path to the <em>git-receive-pack</em> program on the remote
end. Sometimes useful when pushing to a remote
repository over ssh, and you do not have the program in
a directory on the default $PATH.
@@ -420,7 +468,7 @@ nor in any Push line of the corresponding remotes file---see below).</p> </dt>
<dd>
<p>
- These options are passed to <tt>git-send-pack</tt>. Thin
+ These options are passed to <em>git-send-pack</em>. Thin
transfer spends extra cycles to minimize the number of
objects to be sent and meant to be used on slower connection.
</p>
@@ -436,15 +484,15 @@ nor in any Push line of the corresponding remotes file---see below).</p> Run verbosely.
</p>
</dd>
-</dl>
+</dl></div>
</div>
-<h2>GIT URLS<a id="URLS"></a></h2>
+<h2 id="_git_urls_a_id_urls_a">GIT URLS<a id="URLS"></a></h2>
<div class="sectionbody">
-<p>One of the following notations can be used
-to name the remote repository:</p>
+<div class="para"><p>One of the following notations can be used
+to name the remote repository:</p></div>
<div class="exampleblock">
<div class="exampleblock-content">
-<ul>
+<div class="ilist"><ul>
<li>
<p>
rsync://host.xz/path/to/repo.git/
@@ -490,17 +538,17 @@ ssh://[user@]host.xz/~user/path/to/repo.git/ ssh://[user@]host.xz/~/path/to/repo.git
</p>
</li>
-</ul>
+</ul></div>
</div></div>
-<p>SSH is the default transport protocol over the network. You can
+<div class="para"><p>SSH is the default transport protocol over the network. You can
optionally specify which user to log-in as, and an alternate,
scp-like syntax is also supported. Both syntaxes support
username expansion, as does the native git protocol, but
only the former supports port specification. The following
-three are identical to the last three above, respectively:</p>
+three are identical to the last three above, respectively:</p></div>
<div class="exampleblock">
<div class="exampleblock-content">
-<ul>
+<div class="ilist"><ul>
<li>
<p>
[user@]host.xz:/path/to/repo.git/
@@ -516,12 +564,12 @@ three are identical to the last three above, respectively:</p> [user@]host.xz:path/to/repo.git
</p>
</li>
-</ul>
+</ul></div>
</div></div>
-<p>To sync with a local directory, you can use:</p>
+<div class="para"><p>To sync with a local directory, you can use:</p></div>
<div class="exampleblock">
<div class="exampleblock-content">
-<ul>
+<div class="ilist"><ul>
<li>
<p>
/path/to/repo.git/
@@ -532,34 +580,34 @@ three are identical to the last three above, respectively:</p> file:///path/to/repo.git/
</p>
</li>
-</ul>
+</ul></div>
</div></div>
-<p>They are mostly equivalent, except when cloning. See
-<a href="git-clone.html">git-clone(1)</a> for details.</p>
-<p>If there are a large number of similarly-named remote repositories and
+<div class="para"><p>They are mostly equivalent, except when cloning. See
+<a href="git-clone.html">git-clone(1)</a> for details.</p></div>
+<div class="para"><p>If there are a large number of similarly-named remote repositories and
you want to use a different format for them (such that the URLs you
use will be rewritten into URLs that work), you can create a
-configuration section of the form:</p>
+configuration section of the form:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> [url "<actual url base>"]
insteadOf = <other url base></tt></pre>
</div></div>
-<p>For example, with this:</p>
+<div class="para"><p>For example, with this:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> [url "git://git.host.xz/"]
insteadOf = host.xz:/path/to/
insteadOf = work:</tt></pre>
</div></div>
-<p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
-rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".</p>
+<div class="para"><p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
+rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".</p></div>
</div>
-<h2>REMOTES<a id="REMOTES"></a></h2>
+<h2 id="_remotes_a_id_remotes_a">REMOTES<a id="REMOTES"></a></h2>
<div class="sectionbody">
-<p>The name of one of the following can be used instead
-of a URL as <tt><repository></tt> argument:</p>
-<ul>
+<div class="para"><p>The name of one of the following can be used instead
+of a URL as <tt><repository></tt> argument:</p></div>
+<div class="ilist"><ul>
<li>
<p>
a remote in the git configuration file: <tt>$GIT_DIR/config</tt>,
@@ -575,17 +623,17 @@ a file in the <tt>$GIT_DIR/remotes</tt> directory, or a file in the <tt>$GIT_DIR/branches</tt> directory.
</p>
</li>
-</ul>
-<p>All of these also allow you to omit the refspec from the command line
-because they each contain a refspec which git will use by default.</p>
-<h3>Named remote in configuration file</h3>
-<p>You can choose to provide the name of a remote which you had previously
+</ul></div>
+<div class="para"><p>All of these also allow you to omit the refspec from the command line
+because they each contain a refspec which git will use by default.</p></div>
+<h3 id="_named_remote_in_configuration_file">Named remote in configuration file</h3><div style="clear:left"></div>
+<div class="para"><p>You can choose to provide the name of a remote which you had previously
configured using <a href="git-remote.html">git-remote(1)</a>, <a href="git-config.html">git-config(1)</a>
or even by a manual edit to the <tt>$GIT_DIR/config</tt> file. The URL of
this remote will be used to access the repository. The refspec
of this remote will be used by default when you do
not provide a refspec on the command line. The entry in the
-config file would appear like this:</p>
+config file would appear like this:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> [remote "<name>"]
@@ -593,13 +641,13 @@ config file would appear like this:</p> push = <refspec>
fetch = <refspec></tt></pre>
</div></div>
-<h3>Named file in <tt>$GIT_DIR/remotes</tt></h3>
-<p>You can choose to provide the name of a
+<h3 id="_named_file_in_tt_git_dir_remotes_tt">Named file in <tt>$GIT_DIR/remotes</tt></h3><div style="clear:left"></div>
+<div class="para"><p>You can choose to provide the name of a
file in <tt>$GIT_DIR/remotes</tt>. The URL
in this file will be used to access the repository. The refspec
in this file will be used as default when you do not
provide a refspec on the command line. This file should have the
-following format:</p>
+following format:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> URL: one of the above URL format
@@ -607,41 +655,41 @@ following format:</p> Pull: <refspec>
</tt></pre>
</div></div>
-<p><tt>Push:</tt> lines are used by <tt>git-push</tt> and
-<tt>Pull:</tt> lines are used by <tt>git-pull</tt> and <tt>git-fetch</tt>.
+<div class="para"><p><tt>Push:</tt> lines are used by <em>git-push</em> and
+<tt>Pull:</tt> lines are used by <em>git-pull</em> and <em>git-fetch</em>.
Multiple <tt>Push:</tt> and <tt>Pull:</tt> lines may
-be specified for additional branch mappings.</p>
-<h3>Named file in <tt>$GIT_DIR/branches</tt></h3>
-<p>You can choose to provide the name of a
+be specified for additional branch mappings.</p></div>
+<h3 id="_named_file_in_tt_git_dir_branches_tt">Named file in <tt>$GIT_DIR/branches</tt></h3><div style="clear:left"></div>
+<div class="para"><p>You can choose to provide the name of a
file in <tt>$GIT_DIR/branches</tt>.
The URL in this file will be used to access the repository.
-This file should have the following format:</p>
+This file should have the following format:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> <url>#<head></tt></pre>
</div></div>
-<p><tt><url></tt> is required; <tt>#<head></tt> is optional.
+<div class="para"><p><tt><url></tt> is required; <tt>#<head></tt> is optional.
When you do not provide a refspec on the command line,
git will use the following refspec, where <tt><head></tt> defaults to <tt>master</tt>,
and <tt><repository></tt> is the name of this file
-you provided in the command line.</p>
+you provided in the command line.</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> refs/heads/<head>:<repository></tt></pre>
</div></div>
</div>
-<h2>OUTPUT</h2>
+<h2 id="_output">OUTPUT</h2>
<div class="sectionbody">
-<p>The output of "git push" depends on the transport method used; this
+<div class="para"><p>The output of "git push" depends on the transport method used; this
section describes the output when pushing over the git protocol (either
-locally or via ssh).</p>
-<p>The status of the push is output in tabular form, with each line
-representing the status of a single ref. Each line is of the form:</p>
+locally or via ssh).</p></div>
+<div class="para"><p>The status of the push is output in tabular form, with each line
+representing the status of a single ref. Each line is of the form:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> <flag> <summary> <from> -> <to> (<reason>)</tt></pre>
</div></div>
-<dl>
+<div class="vlist"><dl>
<dt>
flag
</dt>
@@ -703,11 +751,11 @@ reason failure is described.
</p>
</dd>
-</dl>
+</dl></div>
</div>
-<h2>Examples</h2>
+<h2 id="_examples">Examples</h2>
<div class="sectionbody">
-<dl>
+<div class="vlist"><dl>
<dt>
git push origin master
</dt>
@@ -752,24 +800,24 @@ git push origin master:refs/heads/experimental the ref name on its own will work.
</p>
</dd>
-</dl>
+</dl></div>
</div>
-<h2>Author</h2>
+<h2 id="_author">Author</h2>
<div class="sectionbody">
-<p>Written by Junio C Hamano <junkio@cox.net>, later rewritten in C
-by Linus Torvalds <torvalds@osdl.org></p>
+<div class="para"><p>Written by Junio C Hamano <junkio@cox.net>, later rewritten in C
+by Linus Torvalds <torvalds@osdl.org></p></div>
</div>
-<h2>Documentation</h2>
+<h2 id="_documentation">Documentation</h2>
<div class="sectionbody">
-<p>Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.</p>
+<div class="para"><p>Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.</p></div>
</div>
-<h2>GIT</h2>
+<h2 id="_git">GIT</h2>
<div class="sectionbody">
-<p>Part of the <a href="git.html">git(1)</a> suite</p>
+<div class="para"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
</div>
<div id="footer">
<div id="footer-text">
-Last updated 02-Jul-2008 03:01:56 UTC
+Last updated 2008-07-06 05:16:57 UTC
</div>
</div>
</body>
|