diff options
| author | Junio C Hamano <gitster@pobox.com> | 2014-10-14 15:28:09 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2014-10-14 15:28:09 -0700 |
| commit | 9236fea47fdd276f1023b03ded5acff2e8d9c213 (patch) | |
| tree | cfde71e833b959ef06d40d4f7ea2a249d8431549 /git-push.html | |
| parent | 6a1de6749fe9b59217f41542aace43daac13b94e (diff) | |
| download | git-htmldocs-9236fea47fdd276f1023b03ded5acff2e8d9c213.tar.gz | |
Autogenerated HTML docs for v2.1.2-443-g670a3
Diffstat (limited to 'git-push.html')
| -rw-r--r-- | git-push.html | 336 |
1 files changed, 173 insertions, 163 deletions
diff --git a/git-push.html b/git-push.html index 2c0dedcab..aeb7c0517 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="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.6" />
+<meta name="generator" content="AsciiDoc 8.6.9" />
<title>git-push(1)</title>
<style type="text/css">
/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
@@ -87,10 +87,16 @@ ul, ol, li > p { ul > li { color: #aaa; }
ul > li > * { color: black; }
-pre {
+.monospaced, code, pre {
+ font-family: "Courier New", Courier, monospace;
+ font-size: inherit;
+ color: navy;
padding: 0;
margin: 0;
}
+pre {
+ white-space: pre-wrap;
+}
#author {
color: #527bbd;
@@ -219,7 +225,7 @@ div.exampleblock > div.content { }
div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
+span.image img { border-style: none; vertical-align: text-bottom; }
a.image:visited { color: white; }
dl {
@@ -349,7 +355,7 @@ div.colist td img { margin-bottom: 0.1em;
}
-div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
+div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
margin-top: 0;
margin-bottom: 0;
}
@@ -407,18 +413,14 @@ span.underline { text-decoration: underline; } span.overline { text-decoration: overline; }
span.line-through { text-decoration: line-through; }
+div.unbreakable { page-break-inside: avoid; }
+
/*
* xhtml11 specific
*
* */
-tt {
- font-family: monospace;
- font-size: inherit;
- color: navy;
-}
-
div.tableblock {
margin-top: 1.0em;
margin-bottom: 1.5em;
@@ -452,12 +454,6 @@ div.tableblock > table[frame="vsides"] { *
* */
-.monospaced {
- font-family: monospace;
- font-size: inherit;
- color: navy;
-}
-
table.tableblock {
margin-top: 1.0em;
margin-bottom: 1.5em;
@@ -537,6 +533,8 @@ body.manpage div.sectionbody { @media print {
body.manpage div#toc { display: none; }
}
+
+
</style>
<script type="text/javascript">
/*<+'])');
+ var re = new RegExp('[hH]([1-'+(toclevels+1)+'])');
// Function that scans the DOM tree for header elements (the DOM2
// nodeIterator API would be a better technique but not supported by all
// browsers).
@@ -610,7 +608,7 @@ toc: function (toclevels) { var i;
for (i = 0; i < toc.childNodes.length; i++) {
var entry = toc.childNodes[i];
- if (entry.nodeName == 'div'
+ if (entry.nodeName.toLowerCase() == 'div'
&& entry.getAttribute("class")
&& entry.getAttribute("class").match(/^toclevel/))
tocEntriesToRemove.push(entry);
@@ -656,7 +654,7 @@ footnotes: function () { var entriesToRemove = [];
for (i = 0; i < noteholder.childNodes.length; i++) {
var entry = noteholder.childNodes[i];
- if (entry.nodeName == 'div' && entry.getAttribute("class") == "footnote")
+ if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
entriesToRemove.push(entry);
}
for (i = 0; i < entriesToRemove.length; i++) {
@@ -751,7 +749,8 @@ git-push(1) Manual Page <div class="sectionbody">
<div class="verseblock">
<pre class="content"><em>git push</em> [--all | --mirror | --tags] [--follow-tags] [-n | --dry-run] [--receive-pack=<git-receive-pack>]
- [--repo=<repository>] [-f | --force] [--prune] [-v | --verbose] [-u | --set-upstream]
+ [--repo=<repository>] [-f | --force] [--prune] [-v | --verbose]
+ [-u | --set-upstream] [--signed]
[--force-with-lease[=<refname>[:<expect>]]]
[--no-verify] [<repository> [<refspec>…]]</pre>
<div class="attribution">
@@ -767,14 +766,14 @@ necessary to complete the given refs.</p></div> 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></div>
<div class="paragraph"><p>When the command line does not specify where to push with the
-<tt><repository></tt> argument, <tt>branch.*.remote</tt> configuration for the
+<code><repository></code> argument, <code>branch.*.remote</code> configuration for the
current branch is consulted to determine where to push. If the
configuration is missing, it defaults to <em>origin</em>.</p></div>
-<div class="paragraph"><p>When the command line does not specify what to push with <tt><refspec>...</tt>
-arguments or <tt>--all</tt>, <tt>--mirror</tt>, <tt>--tags</tt> options, the command finds
-the default <tt><refspec></tt> by consulting <tt>remote.*.push</tt> configuration,
-and if it is not found, honors <tt>push.default</tt> configuration to decide
-what to push (See <a href="git-config.html">git-config(1)</a> for the meaning of <tt>push.default</tt>).</p></div>
+<div class="paragraph"><p>When the command line does not specify what to push with <code><refspec>...</code>
+arguments or <code>--all</code>, <code>--mirror</code>, <code>--tags</code> options, the command finds
+the default <code><refspec></code> by consulting <code>remote.*.push</code> configuration,
+and if it is not found, honors <code>push.default</code> configuration to decide
+what to push (See <a href="git-config.html">git-config(1)</a> for the meaning of <code>push.default</code>).</p></div>
</div>
</div>
<div class="sect1">
@@ -799,32 +798,32 @@ what to push (See <a href="git-config.html">git-config(1)</a> for the meaning of <p>
Specify what destination ref to update with what source object.
The format of a <refspec> parameter is an optional plus
- <tt>+</tt>, followed by the source object <src>, followed
- by a colon <tt>:</tt>, followed by the destination ref <dst>.
+ <code>+</code>, followed by the source object <src>, followed
+ by a colon <code>:</code>, followed by the destination ref <dst>.
</p>
<div class="paragraph"><p>The <src> is often the name of the branch you would want to push, but
-it can be any arbitrary "SHA-1 expression", such as <tt>master~4</tt> or
-<tt>HEAD</tt> (see <a href="gitrevisions.html">gitrevisions(7)</a>).</p></div>
+it can be any arbitrary "SHA-1 expression", such as <code>master~4</code> or
+<code>HEAD</code> (see <a href="gitrevisions.html">gitrevisions(7)</a>).</p></div>
<div class="paragraph"><p>The <dst> tells which ref on the remote side is updated with this
push. Arbitrary expressions cannot be used here, an actual ref must
be named.
-If <tt>git push [<repository>]</tt> without any <tt><refspec></tt> argument is set to
-update some ref at the destination with <tt><src></tt> with
-<tt>remote.<repository>.push</tt> configuration variable, <tt>:<dst></tt> part can
-be omitted---such a push will update a ref that <tt><src></tt> normally updates
-without any <tt><refspec></tt> on the command line. Otherwise, missing
-<tt>:<dst></tt> means to update the same ref as the <tt><src></tt>.</p></div>
+If <code>git push [<repository>]</code> without any <code><refspec></code> argument is set to
+update some ref at the destination with <code><src></code> with
+<code>remote.<repository>.push</code> configuration variable, <code>:<dst></code> part can
+be omitted---such a push will update a ref that <code><src></code> normally updates
+without any <code><refspec></code> on the command line. Otherwise, missing
+<code>:<dst></code> means to update the same ref as the <code><src></code>.</p></div>
<div class="paragraph"><p>The object referenced by <src> is used to update the <dst> reference
on the remote side. By default this is only allowed if <dst> is not
a tag (annotated or lightweight), and then only if it can fast-forward
-<dst>. By having the optional leading <tt>+</tt>, you can tell Git to update
+<dst>. By having the optional leading <code>+</code>, you can tell Git to update
the <dst> ref even if it is not allowed by default (e.g., it is not a
fast-forward.) This does <strong>not</strong> attempt to merge <src> into <dst>. See
EXAMPLES below for details.</p></div>
-<div class="paragraph"><p><tt>tag <tag></tt> means the same as <tt>refs/tags/<tag>:refs/tags/<tag></tt>.</p></div>
+<div class="paragraph"><p><code>tag <tag></code> means the same as <code>refs/tags/<tag>:refs/tags/<tag></code>.</p></div>
<div class="paragraph"><p>Pushing an empty <src> allows you to delete the <dst> ref from
the remote repository.</p></div>
-<div class="paragraph"><p>The special refspec <tt>:</tt> (or <tt>+:</tt> to allow non-fast-forward updates)
+<div class="paragraph"><p>The special refspec <code>:</code> (or <code>+:</code> to allow non-fast-forward updates)
directs Git to push "matching" branches: for every branch that exists on
the local side, the remote side is updated if a branch of the same name
already exists on the remote side.</p></div>
@@ -834,7 +833,7 @@ already exists on the remote side.</p></div> </dt>
<dd>
<p>
- Push all branches (i.e. refs under <tt>refs/heads/</tt>); cannot be
+ Push all branches (i.e. refs under <code>refs/heads/</code>); cannot be
used with other <refspec>.
</p>
</dd>
@@ -844,10 +843,10 @@ already exists on the remote side.</p></div> <dd>
<p>
Remove remote branches that don’t have a local counterpart. For example
- a remote branch <tt>tmp</tt> will be removed if a local branch with the same
+ a remote branch <code>tmp</code> will be removed if a local branch with the same
name doesn’t exist any more. This also respects refspecs, e.g.
- <tt>git push --prune remote refs/heads/*:refs/tmp/*</tt> would
- make sure that remote <tt>refs/tmp/foo</tt> will be removed if <tt>refs/heads/foo</tt>
+ <code>git push --prune remote refs/heads/*:refs/tmp/*</code> would
+ make sure that remote <code>refs/tmp/foo</code> will be removed if <code>refs/heads/foo</code>
doesn’t exist.
</p>
</dd>
@@ -857,13 +856,13 @@ already exists on the remote side.</p></div> <dd>
<p>
Instead of naming each ref to push, specifies that all
- refs under <tt>refs/</tt> (which includes but is not
- limited to <tt>refs/heads/</tt>, <tt>refs/remotes/</tt>, and <tt>refs/tags/</tt>)
+ refs under <code>refs/</code> (which includes but is not
+ limited to <code>refs/heads/</code>, <code>refs/remotes/</code>, and <code>refs/tags/</code>)
be mirrored to the remote repository. Newly created local
refs will be pushed to the remote end, locally updated refs
will be force updated on the remote end, and deleted refs
will be removed from the remote end. This is the default
- if the configuration option <tt>remote.<remote>.mirror</tt> is
+ if the configuration option <code>remote.<remote>.mirror</code> is
set.
</p>
</dd>
@@ -902,7 +901,7 @@ already exists on the remote side.</p></div> </dt>
<dd>
<p>
- All refs under <tt>refs/tags</tt> are pushed, in
+ All refs under <code>refs/tags</code> are pushed, in
addition to refspecs explicitly listed on the command
line.
</p>
@@ -913,12 +912,23 @@ already exists on the remote side.</p></div> <dd>
<p>
Push all the refs that would be pushed without this option,
- and also push annotated tags in <tt>refs/tags</tt> that are missing
+ and also push annotated tags in <code>refs/tags</code> that are missing
from the remote but are pointing at commit-ish that are
reachable from the refs being pushed.
</p>
</dd>
<dt class="hdlist1">
+--signed
+</dt>
+<dd>
+<p>
+ GPG-sign the push request to update refs on the receiving
+ side, to allow it to be checked by the hooks and/or be
+ logged. See <a href="git-receive-pack.html">git-receive-pack(1)</a> for the details
+ on the receiving end.
+</p>
+</dd>
+<dt class="hdlist1">
--receive-pack=<git-receive-pack>
</dt>
<dt class="hdlist1">
@@ -954,29 +964,29 @@ You will have to bypass the "must fast-forward" rule in order to replace the history you originally published with the rebased history.
If somebody else built on top of your original history while you are
rebasing, the tip of the branch at the remote may advance with her
-commit, and blindly pushing with <tt>--force</tt> will lose her work.</p></div>
+commit, and blindly pushing with <code>--force</code> will lose her work.</p></div>
<div class="paragraph"><p>This option allows you to say that you expect the history you are
updating is what you rebased and want to replace. If the remote ref
still points at the commit you specified, you can be sure that no
other people did anything to the ref (it is like taking a "lease" on
the ref without explicitly locking it, and you update the ref while
making sure that your earlier "lease" is still valid).</p></div>
-<div class="paragraph"><p><tt>--force-with-lease</tt> alone, without specifying the details, will protect
+<div class="paragraph"><p><code>--force-with-lease</code> alone, without specifying the details, will protect
all remote refs that are going to be updated by requiring their
current value to be the same as the remote-tracking branch we have
-for them, unless specified with a <tt>--force-with-lease=<refname>:<expect></tt>
+for them, unless specified with a <code>--force-with-lease=<refname>:<expect></code>
option that explicitly states what the expected value is.</p></div>
-<div class="paragraph"><p><tt>--force-with-lease=<refname></tt>, without specifying the expected value, will
+<div class="paragraph"><p><code>--force-with-lease=<refname></code>, without specifying the expected value, will
protect the named ref (alone), if it is going to be updated, by
requiring its current value to be the same as the remote-tracking
branch we have for it.</p></div>
-<div class="paragraph"><p><tt>--force-with-lease=<refname>:<expect></tt> will protect the named ref (alone),
+<div class="paragraph"><p><code>--force-with-lease=<refname>:<expect></code> will protect the named ref (alone),
if it is going to be updated, by requiring its current value to be
the same as the specified value <expect> (which is allowed to be
different from the remote-tracking branch we have for the refname,
or we do not even have to have such a remote-tracking branch when
this form is used).</p></div>
-<div class="paragraph"><p>Note that all forms other than <tt>--force-with-lease=<refname>:<expect></tt>
+<div class="paragraph"><p>Note that all forms other than <code>--force-with-lease=<refname>:<expect></code>
that specifies the expected current value of the ref explicitly are
still experimental and their semantics may change as we gain experience
with this feature.</p></div>
@@ -993,20 +1003,20 @@ command line.</p></div> <p>
Usually, the command refuses to update a remote ref that is
not an ancestor of the local ref used to overwrite it.
- Also, when <tt>--force-with-lease</tt> option is used, the command refuses
+ Also, when <code>--force-with-lease</code> option is used, the command refuses
to update a remote ref whose current value does not match
what is expected.
</p>
<div class="paragraph"><p>This flag disables these checks, and can cause the remote repository
to lose commits; use it with care.</p></div>
-<div class="paragraph"><p>Note that <tt>--force</tt> applies to all the refs that are pushed, hence
-using it with <tt>push.default</tt> set to <tt>matching</tt> or with multiple push
-destinations configured with <tt>remote.*.push</tt> may overwrite refs
+<div class="paragraph"><p>Note that <code>--force</code> applies to all the refs that are pushed, hence
+using it with <code>push.default</code> set to <code>matching</code> or with multiple push
+destinations configured with <code>remote.*.push</code> may overwrite refs
other than the current branch (including local refs that are
strictly behind their remote counterpart). To force a push to only
-one branch, use a <tt>+</tt> in front of the refspec to push (e.g <tt>git push
-origin +master</tt> to force a push to the <tt>master</tt> branch). See the
-<tt><refspec>...</tt> section above for details.</p></div>
+one branch, use a <code>+</code> in front of the refspec to push (e.g <code>git push
+origin +master</code> to force a push to the <code>master</code> branch). See the
+<code><refspec>...</code> section above for details.</p></div>
</dd>
<dt class="hdlist1">
--repo=<repository>
@@ -1023,8 +1033,8 @@ origin +master</tt> to force a push to the <tt>master</tt> branch). See the </p>
<div class="listingblock">
<div class="content">
-<pre><tt>git push public #1
-git push --repo=public #2</tt></pre>
+<pre><code>git push public #1
+git push --repo=public #2</code></pre>
</div></div>
<div class="paragraph"><p>is that #1 always pushes to "public" whereas #2 pushes to "public"
only if the current branch does not track a remote branch. This is
@@ -1170,8 +1180,8 @@ rsync://host.xz/path/to/repo.git/ </ul></div>
<div class="paragraph"><p>This syntax is only recognized if there are no slashes before the
first colon. This helps differentiate a local path that contains a
-colon. For example the local path <tt>foo:bar</tt> could be specified as an
-absolute path or <tt>./foo:bar</tt> to avoid being misinterpreted as an ssh
+colon. For example the local path <code>foo:bar</code> could be specified as an
+absolute path or <code>./foo:bar</code> to avoid being misinterpreted as an ssh
url.</p></div>
<div class="paragraph"><p>The ssh and git protocols additionally support ~username expansion:</p></div>
<div class="ulist"><ul>
@@ -1228,15 +1238,15 @@ use will be rewritten into URLs that work), you can create a 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>
+<pre><code> [url "<actual url base>"]
+ insteadOf = <other url base></code></pre>
</div></div>
<div class="paragraph"><p>For example, with this:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt> [url "git://git.host.xz/"]
+<pre><code> [url "git://git.host.xz/"]
insteadOf = host.xz:/path/to/
- insteadOf = work:</tt></pre>
+ insteadOf = work:</code></pre>
</div></div>
<div class="paragraph"><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>
@@ -1244,14 +1254,14 @@ rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".</p configuration section of the form:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt> [url "<actual url base>"]
- pushInsteadOf = <other url base></tt></pre>
+<pre><code> [url "<actual url base>"]
+ pushInsteadOf = <other url base></code></pre>
</div></div>
<div class="paragraph"><p>For example, with this:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt> [url "ssh://example.org/"]
- pushInsteadOf = git://example.org/</tt></pre>
+<pre><code> [url "ssh://example.org/"]
+ pushInsteadOf = git://example.org/</code></pre>
</div></div>
<div class="paragraph"><p>a URL like "git://example.org/path/to/repo.git" will be rewritten to
"ssh://example.org/path/to/repo.git" for pushes, but pulls will still
@@ -1262,21 +1272,21 @@ use the original URL.</p></div> <h2 id="_remotes_a_id_remotes_a">REMOTES<a id="REMOTES"></a></h2>
<div class="sectionbody">
<div class="paragraph"><p>The name of one of the following can be used instead
-of a URL as <tt><repository></tt> argument:</p></div>
+of a URL as <code><repository></code> argument:</p></div>
<div class="ulist"><ul>
<li>
<p>
-a remote in the Git configuration file: <tt>$GIT_DIR/config</tt>,
+a remote in the Git configuration file: <code>$GIT_DIR/config</code>,
</p>
</li>
<li>
<p>
-a file in the <tt>$GIT_DIR/remotes</tt> directory, or
+a file in the <code>$GIT_DIR/remotes</code> directory, or
</p>
</li>
<li>
<p>
-a file in the <tt>$GIT_DIR/branches</tt> directory.
+a file in the <code>$GIT_DIR/branches</code> directory.
</p>
</li>
</ul></div>
@@ -1286,65 +1296,65 @@ 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 class="paragraph"><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
+or even by a manual edit to the <code>$GIT_DIR/config</code> 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></div>
<div class="listingblock">
<div class="content">
-<pre><tt> [remote "<name>"]
+<pre><code> [remote "<name>"]
url = <url>
pushurl = <pushurl>
push = <refspec>
- fetch = <refspec></tt></pre>
+ fetch = <refspec></code></pre>
</div></div>
-<div class="paragraph"><p>The <tt><pushurl></tt> is used for pushes only. It is optional and defaults
-to <tt><url></tt>.</p></div>
+<div class="paragraph"><p>The <code><pushurl></code> is used for pushes only. It is optional and defaults
+to <code><url></code>.</p></div>
</div>
<div class="sect2">
-<h3 id="_named_file_in_tt_git_dir_remotes_tt">Named file in <tt>$GIT_DIR/remotes</tt></h3>
+<h3 id="_named_file_in_code_git_dir_remotes_code">Named file in <code>$GIT_DIR/remotes</code></h3>
<div class="paragraph"><p>You can choose to provide the name of a
-file in <tt>$GIT_DIR/remotes</tt>. The URL
+file in <code>$GIT_DIR/remotes</code>. 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></div>
<div class="listingblock">
<div class="content">
-<pre><tt> URL: one of the above URL format
+<pre><code> URL: one of the above URL format
Push: <refspec>
- Pull: <refspec></tt></pre>
+ Pull: <refspec></code></pre>
</div></div>
-<div class="paragraph"><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
+<div class="paragraph"><p><code>Push:</code> lines are used by <em>git push</em> and
+<code>Pull:</code> lines are used by <em>git pull</em> and <em>git fetch</em>.
+Multiple <code>Push:</code> and <code>Pull:</code> lines may
be specified for additional branch mappings.</p></div>
</div>
<div class="sect2">
-<h3 id="_named_file_in_tt_git_dir_branches_tt">Named file in <tt>$GIT_DIR/branches</tt></h3>
+<h3 id="_named_file_in_code_git_dir_branches_code">Named file in <code>$GIT_DIR/branches</code></h3>
<div class="paragraph"><p>You can choose to provide the name of a
-file in <tt>$GIT_DIR/branches</tt>.
+file in <code>$GIT_DIR/branches</code>.
The URL in this file will be used to access the repository.
This file should have the following format:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt> <url>#<head></tt></pre>
+<pre><code> <url>#<head></code></pre>
</div></div>
-<div class="paragraph"><p><tt><url></tt> is required; <tt>#<head></tt> is optional.</p></div>
+<div class="paragraph"><p><code><url></code> is required; <code>#<head></code> is optional.</p></div>
<div class="paragraph"><p>Depending on the operation, git will use one of the following
refspecs, if you don’t provide one on the command line.
-<tt><branch></tt> is the name of this file in <tt>$GIT_DIR/branches</tt> and
-<tt><head></tt> defaults to <tt>master</tt>.</p></div>
+<code><branch></code> is the name of this file in <code>$GIT_DIR/branches</code> and
+<code><head></code> defaults to <code>master</code>.</p></div>
<div class="paragraph"><p>git fetch uses:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt> refs/heads/<head>:refs/heads/<branch></tt></pre>
+<pre><code> refs/heads/<head>:refs/heads/<branch></code></pre>
</div></div>
<div class="paragraph"><p>git push uses:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt> HEAD:refs/heads/<head></tt></pre>
+<pre><code> HEAD:refs/heads/<head></code></pre>
</div></div>
</div>
</div>
@@ -1359,12 +1369,12 @@ locally or via ssh).</p></div> 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>
+<pre><code> <flag> <summary> <from> -> <to> (<reason>)</code></pre>
</div></div>
<div class="paragraph"><p>If --porcelain is used, then each line of the output is of the form:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt> <flag> \t <from>:<to> \t <summary> (<reason>)</tt></pre>
+<pre><code> <flag> \t <from>:<to> \t <summary> (<reason>)</code></pre>
</div></div>
<div class="paragraph"><p>The status of up-to-date refs is shown only if --porcelain or --verbose
option is used.</p></div>
@@ -1386,7 +1396,7 @@ for a successfully pushed fast-forward; </p>
</dd>
<dt class="hdlist1">
-<tt>+</tt>
+<code>+</code>
</dt>
<dd>
<p>
@@ -1394,7 +1404,7 @@ for a successful forced update; </p>
</dd>
<dt class="hdlist1">
-<tt>-</tt>
+<code>-</code>
</dt>
<dd>
<p>
@@ -1402,7 +1412,7 @@ for a successfully deleted ref; </p>
</dd>
<dt class="hdlist1">
-<tt>*</tt>
+<code>*</code>
</dt>
<dd>
<p>
@@ -1410,7 +1420,7 @@ for a successfully pushed new ref; </p>
</dd>
<dt class="hdlist1">
-<tt>!</tt>
+<code>!</code>
</dt>
<dd>
<p>
@@ -1418,7 +1428,7 @@ for a ref that was rejected or failed to push; and </p>
</dd>
<dt class="hdlist1">
-<tt>=</tt>
+<code>=</code>
</dt>
<dd>
<p>
@@ -1434,8 +1444,8 @@ summary <p>
For a successfully pushed ref, the summary shows the old and new
values of the ref in a form suitable for using as an argument to
- <tt>git log</tt> (this is <tt><old>..<new></tt> in most cases, and
- <tt><old>...<new></tt> for forced non-fast-forward updates).
+ <code>git log</code> (this is <code><old>..<new></code> in most cases, and
+ <code><old>...<new></code> for forced non-fast-forward updates).
</p>
<div class="paragraph"><p>For a failed update, more details are given:</p></div>
<div class="openblock">
@@ -1458,10 +1468,10 @@ remote rejected The remote end refused the update. Usually caused by a hook
on the remote side, or because the remote repository has one
of the following safety options in effect:
- <tt>receive.denyCurrentBranch</tt> (for pushes to the checked out
- branch), <tt>receive.denyNonFastForwards</tt> (for forced
- non-fast-forward updates), <tt>receive.denyDeletes</tt> or
- <tt>receive.denyDeleteCurrent</tt>. See <a href="git-config.html">git-config(1)</a>.
+ <code>receive.denyCurrentBranch</code> (for pushes to the checked out
+ branch), <code>receive.denyNonFastForwards</code> (for forced
+ non-fast-forward updates), <code>receive.denyDeletes</code> or
+ <code>receive.denyDeleteCurrent</code>. See <a href="git-config.html">git-config(1)</a>.
</p>
</dd>
<dt class="hdlist1">
@@ -1483,7 +1493,7 @@ from <dd>
<p>
The name of the local ref being pushed, minus its
- <tt>refs/<type>/</tt> prefix. In the case of deletion, the
+ <code>refs/<type>/</code> prefix. In the case of deletion, the
name of the local ref is omitted.
</p>
</dd>
@@ -1493,7 +1503,7 @@ to <dd>
<p>
The name of the remote ref being updated, minus its
- <tt>refs/<type>/</tt> prefix.
+ <code>refs/<type>/</code> prefix.
</p>
</dd>
<dt class="hdlist1">
@@ -1524,9 +1534,9 @@ a history leading to commit B while the other person built a history leading to commit A. The history looks like this:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt> B
+<pre><code> B
/
- ---X---A</tt></pre>
+ ---X---A</code></pre>
</div></div>
<div class="paragraph"><p>Further suppose that the other person already pushed changes leading to A
back to the original repository from which you two obtained the original
@@ -1548,9 +1558,9 @@ the result. A "git pull" will create a merge commit C between commits A and B.</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt> B---C
+<pre><code> B---C
/ /
- ---X---A</tt></pre>
+ ---X---A</code></pre>
</div></div>
<div class="paragraph"><p>Updating A with the resulting merge commit will fast-forward and your
push will be accepted.</p></div>
@@ -1560,9 +1570,9 @@ create a new commit D that builds the change between X and B on top of A.</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt> B D
+<pre><code> B D
/ /
- ---X---A</tt></pre>
+ ---X---A</code></pre>
</div></div>
<div class="paragraph"><p>Again, updating A with this commit will fast-forward and your push will be
accepted.</p></div>
@@ -1583,57 +1593,57 @@ a case where you do mean to lose history.</p></div> <div class="sectionbody">
<div class="dlist"><dl>
<dt class="hdlist1">
-<tt>git push</tt>
+<code>git push</code>
</dt>
<dd>
<p>
- Works like <tt>git push <remote></tt>, where <remote> is the
- current branch’s remote (or <tt>origin</tt>, if no remote is
+ Works like <code>git push <remote></code>, where <remote> is the
+ current branch’s remote (or <code>origin</code>, if no remote is
configured for the current branch).
</p>
</dd>
<dt class="hdlist1">
-<tt>git push origin</tt>
+<code>git push origin</code>
</dt>
<dd>
<p>
Without additional configuration, pushes the current branch to
- the configured upstream (<tt>remote.origin.merge</tt> configuration
+ the configured upstream (<code>remote.origin.merge</code> configuration
variable) if it has the same name as the current branch, and
errors out without pushing otherwise.
</p>
<div class="paragraph"><p>The default behavior of this command when no <refspec> is given can be
-configured by setting the <tt>push</tt> option of the remote, or the <tt>push.default</tt>
+configured by setting the <code>push</code> option of the remote, or the <code>push.default</code>
configuration variable.</p></div>
-<div class="paragraph"><p>For example, to default to pushing only the current branch to <tt>origin</tt>
-use <tt>git config remote.origin.push HEAD</tt>. Any valid <refspec> (like
+<div class="paragraph"><p>For example, to default to pushing only the current branch to <code>origin</code>
+use <code>git config remote.origin.push HEAD</code>. Any valid <refspec> (like
the ones in the examples below) can be configured as the default for
-<tt>git push origin</tt>.</p></div>
+<code>git push origin</code>.</p></div>
</dd>
<dt class="hdlist1">
-<tt>git push origin :</tt>
+<code>git push origin :</code>
</dt>
<dd>
<p>
- Push "matching" branches to <tt>origin</tt>. See
+ Push "matching" branches to <code>origin</code>. See
<refspec> in the <a href="#OPTIONS">OPTIONS</a> section above for a
description of "matching" branches.
</p>
</dd>
<dt class="hdlist1">
-<tt>git push origin master</tt>
+<code>git push origin master</code>
</dt>
<dd>
<p>
- Find a ref that matches <tt>master</tt> in the source repository
- (most likely, it would find <tt>refs/heads/master</tt>), and update
- the same ref (e.g. <tt>refs/heads/master</tt>) in <tt>origin</tt> repository
- with it. If <tt>master</tt> did not exist remotely, it would be
+ Find a ref that matches <code>master</code> in the source repository
+ (most likely, it would find <code>refs/heads/master</code>), and update
+ the same ref (e.g. <code>refs/heads/master</code>) in <code>origin</code> repository
+ with it. If <code>master</code> did not exist remotely, it would be
created.
</p>
</dd>
<dt class="hdlist1">
-<tt>git push origin HEAD</tt>
+<code>git push origin HEAD</code>
</dt>
<dd>
<p>
@@ -1642,59 +1652,59 @@ the ones in the examples below) can be configured as the default for </p>
</dd>
<dt class="hdlist1">
-<tt>git push mothership master:satellite/master dev:satellite/dev</tt>
+<code>git push mothership master:satellite/master dev:satellite/dev</code>
</dt>
<dd>
<p>
- Use the source ref that matches <tt>master</tt> (e.g. <tt>refs/heads/master</tt>)
- to update the ref that matches <tt>satellite/master</tt> (most probably
- <tt>refs/remotes/satellite/master</tt>) in the <tt>mothership</tt> repository;
- do the same for <tt>dev</tt> and <tt>satellite/dev</tt>.
+ Use the source ref that matches <code>master</code> (e.g. <code>refs/heads/master</code>)
+ to update the ref that matches <code>satellite/master</code> (most probably
+ <code>refs/remotes/satellite/master</code>) in the <code>mothership</code> repository;
+ do the same for <code>dev</code> and <code>satellite/dev</code>.
</p>
-<div class="paragraph"><p>This is to emulate <tt>git fetch</tt> run on the <tt>mothership</tt> using <tt>git
-push</tt> that is run in the opposite direction in order to integrate
-the work done on <tt>satellite</tt>, and is often necessary when you can
+<div class="paragraph"><p>This is to emulate <code>git fetch</code> run on the <code>mothership</code> using <code>git
+push</code> that is run in the opposite direction in order to integrate
+the work done on <code>satellite</code>, and is often necessary when you can
only make connection in one way (i.e. satellite can ssh into
mothership but mothership cannot initiate connection to satellite
because the latter is behind a firewall or does not run sshd).</p></div>
-<div class="paragraph"><p>After running this <tt>git push</tt> on the <tt>satellite</tt> machine, you would
-ssh into the <tt>mothership</tt> and run <tt>git merge</tt> there to complete the
-emulation of <tt>git pull</tt> that were run on <tt>mothership</tt> to pull changes
-made on <tt>satellite</tt>.</p></div>
+<div class="paragraph"><p>After running this <code>git push</code> on the <code>satellite</code> machine, you would
+ssh into the <code>mothership</code> and run <code>git merge</code> there to complete the
+emulation of <code>git pull</code> that were run on <code>mothership</code> to pull changes
+made on <code>satellite</code>.</p></div>
</dd>
<dt class="hdlist1">
-<tt>git push origin HEAD:master</tt>
+<code>git push origin HEAD:master</code>
</dt>
<dd>
<p>
- Push the current branch to the remote ref matching <tt>master</tt> in the
- <tt>origin</tt> repository. This form is convenient to push the current
+ Push the current branch to the remote ref matching <code>master</code> in the
+ <code>origin</code> repository. This form is convenient to push the current
branch without thinking about its local name.
</p>
</dd>
<dt class="hdlist1">
-<tt>git push origin master:refs/heads/experimental</tt>
+<code>git push origin master:refs/heads/experimental</code>
</dt>
<dd>
<p>
- Create the branch <tt>experimental</tt> in the <tt>origin</tt> repository
- by copying the current <tt>master</tt> branch. This form is only
+ Create the branch <code>experimental</code> in the <code>origin</code> repository
+ by copying the current <code>master</code> branch. This form is only
needed to create a new branch or tag in the remote repository when
the local name and the remote name are different; otherwise,
the ref name on its own will work.
</p>
</dd>
<dt class="hdlist1">
-<tt>git push origin :experimental</tt>
+<code>git push origin :experimental</code>
</dt>
<dd>
<p>
- Find a ref that matches <tt>experimental</tt> in the <tt>origin</tt> repository
- (e.g. <tt>refs/heads/experimental</tt>), and delete it.
+ Find a ref that matches <code>experimental</code> in the <code>origin</code> repository
+ (e.g. <code>refs/heads/experimental</code>), and delete it.
</p>
</dd>
<dt class="hdlist1">
-<tt>git push origin +dev:master</tt>
+<code>git push origin +dev:master</code>
</dt>
<dd>
<p>
@@ -1705,20 +1715,20 @@ made on <tt>satellite</tt>.</p></div> </p>
<div class="listingblock">
<div class="content">
-<pre><tt> o---o---o---A---B origin/master
+<pre><code> o---o---o---A---B origin/master
\
- X---Y---Z dev</tt></pre>
+ X---Y---Z dev</code></pre>
</div></div>
<div class="paragraph"><p>The above command would change the origin repository to</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt> A---B (unnamed branch)
+<pre><code> A---B (unnamed branch)
/
- o---o---o---X---Y---Z master</tt></pre>
+ o---o---o---X---Y---Z master</code></pre>
</div></div>
<div class="paragraph"><p>Commits A and B would no longer belong to a branch with a symbolic name,
and so would be unreachable. As such, these commits would be removed by
-a <tt>git gc</tt> command on the origin repository.</p></div>
+a <code>git gc</code> command on the origin repository.</p></div>
</dd>
</dl></div>
</div>
@@ -1733,7 +1743,7 @@ a <tt>git gc</tt> command on the origin repository.</p></div> <div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2014-08-04 14:37:24 PDT
+Last updated 2014-10-14 15:27:06 PDT
</div>
</div>
</body>
|