diff options
| author | Junio C Hamano <junio@kernel.org> | 2010-11-06 01:01:59 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@kernel.org> | 2010-11-06 01:01:59 +0000 |
| commit | 68cf15a825368c926443c26a6516947fca3c1d39 (patch) | |
| tree | a587c9a51372746ddc3cdb08108bb14fb94a0488 /git-fetch.html | |
| parent | 39c7a69d994a13cbd5594bf2f5e65a0f21cc9bb9 (diff) | |
| download | git-htmldocs-68cf15a825368c926443c26a6516947fca3c1d39.tar.gz | |
Autogenerated HTML docs for v1.7.3.2-161-g3089c
Diffstat (limited to 'git-fetch.html')
| -rw-r--r-- | git-fetch.html | 319 |
1 files changed, 206 insertions, 113 deletions
diff --git a/git-fetch.html b/git-fetch.html index 10d3285c4..1ab64a4b8 100644 --- a/git-fetch.html +++ b/git-fetch.html @@ -3,7 +3,8 @@ <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 8.2.5" />
+<meta name="generator" content="AsciiDoc 8.4.5" />
+<title>git-fetch(1)</title>
<style type="text/css">
/* Debug borders */
p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
@@ -26,10 +27,12 @@ a:visited { em {
font-style: italic;
+ color: navy;
}
strong {
font-weight: bold;
+ color: #083194;
}
tt {
@@ -71,6 +74,10 @@ p { margin-bottom: 0.5em;
}
+ul, ol, li > p {
+ margin-top: 0;
+}
+
pre {
padding: 0;
margin: 0;
@@ -84,7 +91,7 @@ span#author { }
span#email {
}
-span#revision {
+span#revnumber, span#revdate, span#revremark {
font-family: sans-serif;
}
@@ -104,11 +111,13 @@ div#footer-badges { padding-bottom: 0.5em;
}
-div#preamble,
+div#preamble {
+ margin-top: 1.5em;
+ margin-bottom: 1.5em;
+}
div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
div.admonitionblock {
- margin-right: 10%;
margin-top: 1.5em;
margin-bottom: 1.5em;
}
@@ -123,6 +132,7 @@ div.content { /* Block element content. */ /* Block element titles. */
div.title, caption.title {
+ color: #527bbd;
font-family: sans-serif;
font-weight: bold;
text-align: left;
@@ -149,22 +159,33 @@ div.sidebarblock > div.content { padding: 0.5em;
}
-div.listingblock {
- margin-right: 0%;
-}
div.listingblock > div.content {
border: 1px solid silver;
background: #f4f4f4;
padding: 0.5em;
}
-div.quoteblock > div.content {
+div.quoteblock {
padding-left: 2.0em;
+ margin-right: 10%;
}
-
-div.attribution {
+div.quoteblock > div.attribution {
+ padding-top: 0.5em;
text-align: right;
}
+
+div.verseblock {
+ padding-left: 2.0em;
+ margin-right: 10%;
+}
+div.verseblock > div.content {
+ white-space: pre;
+}
+div.verseblock > div.attribution {
+ padding-top: 0.75em;
+ text-align: left;
+}
+/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
div.verseblock + div.attribution {
text-align: left;
}
@@ -187,13 +208,9 @@ div.exampleblock > div.content { padding: 0.5em;
}
-div.verseblock div.content {
- white-space: pre;
-}
-
div.imageblock div.content { padding-left: 0; }
-div.imageblock img { border: 1px solid silver; }
span.image img { border-style: none; }
+a.image:visited { color: white; }
dl {
margin-top: 0.8em;
@@ -202,18 +219,38 @@ dl { dt {
margin-top: 0.5em;
margin-bottom: 0;
- font-style: italic;
+ font-style: normal;
+ color: navy;
}
dd > *:first-child {
- margin-top: 0;
+ margin-top: 0.1em;
}
ul, ol {
list-style-position: outside;
}
-div.olist2 ol {
+ol.arabic {
+ list-style-type: decimal;
+}
+ol.loweralpha {
list-style-type: lower-alpha;
}
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+div.compact ul, div.compact ol,
+div.compact p, div.compact p,
+div.compact div, div.compact div {
+ margin-top: 0.1em;
+ margin-bottom: 0.1em;
+}
div.tableblock > table {
border: 3px solid #527bbd;
@@ -225,22 +262,53 @@ thead { tfoot {
font-weight: bold;
}
+td > div.verse {
+ white-space: pre;
+}
+p.table {
+ margin-top: 0;
+}
+/* Because the table frame attribute is overriden by CSS in most browsers. */
+div.tableblock > table[frame="void"] {
+ border-style: none;
+}
+div.tableblock > table[frame="hsides"] {
+ border-left-style: none;
+ border-right-style: none;
+}
+div.tableblock > table[frame="vsides"] {
+ border-top-style: none;
+ border-bottom-style: none;
+}
-div.hlist {
+
+div.hdlist {
margin-top: 0.8em;
margin-bottom: 0.8em;
}
-div.hlist td {
- padding-bottom: 5px;
+div.hdlist tr {
+ padding-bottom: 15px;
+}
+dt.hdlist1.strong, td.hdlist1.strong {
+ font-weight: bold;
}
-td.hlist1 {
+td.hdlist1 {
vertical-align: top;
- font-style: italic;
+ font-style: normal;
padding-right: 0.8em;
+ color: navy;
}
-td.hlist2 {
+td.hdlist2 {
vertical-align: top;
}
+div.hdlist.compact tr {
+ margin: 0;
+ padding-bottom: 0;
+}
+
+.comment {
+ background: yellow;
+}
@media print {
div#footer-badges { display: none; }
@@ -271,7 +339,24 @@ div.toclevel4 { margin-left: 6em;
font-size: 0.9em;
}
-include1::./stylesheets/xhtml11-manpage.css[]
+/* Overrides for manpage documents */
+h1 {
+ padding-top: 0.5em;
+ padding-bottom: 0.5em;
+ border-top: 2px solid silver;
+ border-bottom: 2px solid silver;
+}
+h2 {
+ border-style: none;
+}
+div.sectionbody {
+ margin-left: 5%;
+}
+
+@media print {
+ div#toc { display: none; }
+}
+
/* Workarounds for IE6's broken and incomplete CSS2. */
div.sidebar-content {
@@ -280,6 +365,7 @@ div.sidebar-content { padding: 0.5em;
}
div.sidebar-title, div.image-title {
+ color: #527bbd;
font-family: sans-serif;
font-weight: bold;
margin-top: 0.0em;
@@ -292,8 +378,17 @@ div.listingblock div.content { padding: 0.5em;
}
-div.quoteblock-content {
- padding-left: 2.0em;
+div.quoteblock-attribution {
+ padding-top: 0.5em;
+ text-align: right;
+}
+
+div.verseblock-content {
+ white-space: pre;
+}
+div.verseblock-attribution {
+ padding-top: 0.75em;
+ text-align: left;
}
div.exampleblock-content {
@@ -304,7 +399,6 @@ div.exampleblock-content { /* IE6 sets dynamically generated links as visited. */
div#toc a:visited { color: blue; }
</style>
-<title>git-fetch(1)</title>
</head>
<body>
<div id="header">
@@ -318,36 +412,36 @@ git-fetch(1) Manual Page </p>
</div>
</div>
-<h2>SYNOPSIS</h2>
+<h2 id="_synopsis">SYNOPSIS</h2>
<div class="sectionbody">
-<div class="para"><p><em>git fetch</em> [<options>] [<repository> [<refspec>…]]</p></div>
-<div class="para"><p><em>git fetch</em> [<options>] <group></p></div>
-<div class="para"><p><em>git fetch</em> --multiple [<options>] [(<repository> | <group>)…]</p></div>
-<div class="para"><p><em>git fetch</em> --all [<options>]</p></div>
+<div class="paragraph"><p><em>git fetch</em> [<options>] [<repository> [<refspec>…]]</p></div>
+<div class="paragraph"><p><em>git fetch</em> [<options>] <group></p></div>
+<div class="paragraph"><p><em>git fetch</em> --multiple [<options>] [(<repository> | <group>)…]</p></div>
+<div class="paragraph"><p><em>git fetch</em> --all [<options>]</p></div>
</div>
<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
-<div class="para"><p>Fetches named heads or tags from one or more other repositories,
+<div class="paragraph"><p>Fetches named heads or tags from one or more other repositories,
along with the objects necessary to complete them.</p></div>
-<div class="para"><p>The ref names and their object names of fetched refs are stored
+<div class="paragraph"><p>The ref names and their object names of fetched refs are stored
in <tt>.git/FETCH_HEAD</tt>. This information is left for a later merge
operation done by <em>git merge</em>.</p></div>
-<div class="para"><p>When <refspec> stores the fetched result in tracking branches,
+<div class="paragraph"><p>When <refspec> stores the fetched result in tracking branches,
the tags that point at these branches are automatically
followed. This is done by first fetching from the remote using
the given <refspec>s, and if the repository has objects that are
pointed by remote tags that it does not yet have, then fetch
those missing tags. If the other end has tags that point at
branches you are not interested in, you will not get them.</p></div>
-<div class="para"><p><em>git fetch</em> can fetch from either a single named repository, or
+<div class="paragraph"><p><em>git fetch</em> can fetch from either a single named repository, or
or from several repositories at once if <group> is given and
there is a remotes.<group> entry in the configuration file.
(See <a href="git-config.html">git-config(1)</a>).</p></div>
</div>
<h2 id="_options">OPTIONS</h2>
<div class="sectionbody">
-<div class="vlist"><dl>
-<dt>
+<div class="dlist"><dl>
+<dt class="hdlist1">
--all
</dt>
<dd>
@@ -355,10 +449,10 @@ there is a remotes.<group> entry in the configuration file. Fetch all remotes.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
-a
</dt>
-<dt>
+<dt class="hdlist1">
--append
</dt>
<dd>
@@ -368,7 +462,7 @@ there is a remotes.<group> entry in the configuration file. option old data in <tt>.git/FETCH_HEAD</tt> will be overwritten.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--depth=<depth>
</dt>
<dd>
@@ -378,7 +472,7 @@ there is a remotes.<group> entry in the configuration file. by the specified number of commits.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--dry-run
</dt>
<dd>
@@ -386,10 +480,10 @@ there is a remotes.<group> entry in the configuration file. Show what would be done, without making any changes.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
-f
</dt>
-<dt>
+<dt class="hdlist1">
--force
</dt>
<dd>
@@ -401,10 +495,10 @@ there is a remotes.<group> entry in the configuration file. overrides that check.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
-k
</dt>
-<dt>
+<dt class="hdlist1">
--keep
</dt>
<dd>
@@ -412,7 +506,7 @@ there is a remotes.<group> entry in the configuration file. Keep downloaded pack.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--multiple
</dt>
<dd>
@@ -421,10 +515,10 @@ there is a remotes.<group> entry in the configuration file. specified. No <refspec>s may be specified.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
-p
</dt>
-<dt>
+<dt class="hdlist1">
--prune
</dt>
<dd>
@@ -433,10 +527,10 @@ there is a remotes.<group> entry in the configuration file. no longer exist on the remote.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
-n
</dt>
-<dt>
+<dt class="hdlist1">
--no-tags
</dt>
<dd>
@@ -448,10 +542,10 @@ there is a remotes.<group> entry in the configuration file. setting. See <a href="git-config.html">git-config(1)</a>.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
-t
</dt>
-<dt>
+<dt class="hdlist1">
--tags
</dt>
<dd>
@@ -466,10 +560,10 @@ there is a remotes.<group> entry in the configuration file. <a href="git-config.html">git-config(1)</a>.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
-u
</dt>
-<dt>
+<dt class="hdlist1">
--update-head-ok
</dt>
<dd>
@@ -482,7 +576,7 @@ there is a remotes.<group> entry in the configuration file. use it.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--upload-pack <upload-pack>
</dt>
<dd>
@@ -493,10 +587,10 @@ there is a remotes.<group> entry in the configuration file. run on the other end.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
-q
</dt>
-<dt>
+<dt class="hdlist1">
--quiet
</dt>
<dd>
@@ -506,10 +600,10 @@ there is a remotes.<group> entry in the configuration file. stream.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
-v
</dt>
-<dt>
+<dt class="hdlist1">
--verbose
</dt>
<dd>
@@ -517,7 +611,7 @@ there is a remotes.<group> entry in the configuration file. Be verbose.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
--progress
</dt>
<dd>
@@ -528,7 +622,7 @@ there is a remotes.<group> entry in the configuration file. standard error stream is not directed to a terminal.
</p>
</dd>
-<dt>
+<dt class="hdlist1">
<repository>
</dt>
<dd>
@@ -539,7 +633,7 @@ there is a remotes.<group> entry in the configuration file. of a remote (see the section <a href="#REMOTES">REMOTES</a> below).
</p>
</dd>
-<dt>
+<dt class="hdlist1">
<group>
</dt>
<dd>
@@ -549,7 +643,7 @@ there is a remotes.<group> entry in the configuration file. (See <a href="git-config.html">git-config(1)</a>).
</p>
</dd>
-<dt>
+<dt class="hdlist1">
<refspec>
</dt>
<dd>
@@ -558,7 +652,7 @@ there is a remotes.<group> entry in the configuration file. <tt>+</tt>, followed by the source ref <src>, followed
by a colon <tt>:</tt>, followed by the destination ref <dst>.
</p>
-<div class="para"><p>The remote ref that matches <src>
+<div class="paragraph"><p>The remote ref that matches <src>
is fetched, and if <dst> is not empty string, the local
ref that matches it is fast-forwarded using <src>.
If the optional plus <tt>+</tt> is used, the local ref
@@ -620,8 +714,8 @@ of multiple remote heads in one-go by fetching more than one is often useful.</td>
</tr></table>
</div>
-<div class="para"><p>Some short-cut notations are also supported.</p></div>
-<div class="ilist"><ul>
+<div class="paragraph"><p>Some short-cut notations are also supported.</p></div>
+<div class="ulist"><ul>
<li>
<p>
<tt>tag <tag></tt> means the same as <tt>refs/tags/<tag>:refs/tags/<tag></tt>;
@@ -641,13 +735,13 @@ A parameter <ref> without a colon is equivalent to </div>
<h2 id="_git_urls_a_id_urls_a">GIT URLS<a id="URLS"></a></h2>
<div class="sectionbody">
-<div class="para"><p>In general, URLs contain information about the transport protocol, the
+<div class="paragraph"><p>In general, URLs contain information about the transport protocol, the
address of the remote server, and the path to the repository.
Depending on the transport protocol, some of this information may be
absent.</p></div>
-<div class="para"><p>Git natively supports ssh, git, http, https, ftp, ftps, and rsync
+<div class="paragraph"><p>Git natively supports ssh, git, http, https, ftp, ftps, and rsync
protocols. The following syntaxes may be used with them:</p></div>
-<div class="ilist"><ul>
+<div class="ulist"><ul>
<li>
<p>
ssh://[user@]host.xz[:port]/path/to/repo.git/
@@ -674,16 +768,16 @@ rsync://host.xz/path/to/repo.git/ </p>
</li>
</ul></div>
-<div class="para"><p>An alternative scp-like syntax may also be used with the ssh protocol:</p></div>
-<div class="ilist"><ul>
+<div class="paragraph"><p>An alternative scp-like syntax may also be used with the ssh protocol:</p></div>
+<div class="ulist"><ul>
<li>
<p>
[user@]host.xz:path/to/repo.git/
</p>
</li>
</ul></div>
-<div class="para"><p>The ssh and git protocols additionally support ~username expansion:</p></div>
-<div class="ilist"><ul>
+<div class="paragraph"><p>The ssh and git protocols additionally support ~username expansion:</p></div>
+<div class="ulist"><ul>
<li>
<p>
ssh://[user@]host.xz[:port]/~[user]/path/to/repo.git/
@@ -700,9 +794,9 @@ git://host.xz[:port]/~[user]/path/to/repo.git/ </p>
</li>
</ul></div>
-<div class="para"><p>For local repositories, also supported by git natively, the following
+<div class="paragraph"><p>For local repositories, also supported by git natively, the following
syntaxes may be used:</p></div>
-<div class="ilist"><ul>
+<div class="ulist"><ul>
<li>
<p>
/path/to/repo.git/
@@ -710,28 +804,28 @@ syntaxes may be used:</p></div> </li>
<li>
<p>
-file:///path/to/repo.git/
+<a href="file:///path/to/repo.git/">file:///path/to/repo.git/</a>
</p>
</li>
</ul></div>
-<div class="para"><p>These two syntaxes are mostly equivalent, except when cloning, when
+<div class="paragraph"><p>These two syntaxes are mostly equivalent, except when cloning, when
the former implies --local option. See <a href="git-clone.html">git-clone(1)</a> for
details.</p></div>
-<div class="para"><p>When git doesn't know how to handle a certain transport protocol, it
+<div class="paragraph"><p>When git doesn’t know how to handle a certain transport protocol, it
attempts to use the <em>remote-<transport></em> remote helper, if one
exists. To explicitly request a remote helper, the following syntax
may be used:</p></div>
-<div class="ilist"><ul>
+<div class="ulist"><ul>
<li>
<p>
<transport>::<address>
</p>
</li>
</ul></div>
-<div class="para"><p>where <address> may be a path, a server and path, or an arbitrary
+<div class="paragraph"><p>where <address> may be a path, a server and path, or an arbitrary
URL-like string recognized by the specific remote helper being
invoked. See <a href="git-remote-helpers.html">git-remote-helpers(1)</a> for details.</p></div>
-<div class="para"><p>If there are a large number of similarly-named remote repositories and
+<div class="paragraph"><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></div>
@@ -740,37 +834,37 @@ configuration section of the form:</p></div> <pre><tt> [url "<actual url base>"]
insteadOf = <other url base></tt></pre>
</div></div>
-<div class="para"><p>For example, with this:</p></div>
+<div class="paragraph"><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>
-<div class="para"><p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
+<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>
-<div class="para"><p>If you want to rewrite URLs for push only, you can create a
+<div class="paragraph"><p>If you want to rewrite URLs for push only, you can create a
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>
</div></div>
-<div class="para"><p>For example, with this:</p></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>
</div></div>
-<div class="para"><p>a URL like "git://example.org/path/to/repo.git" will be rewritten to
+<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
use the original URL.</p></div>
</div>
<h2 id="_remotes_a_id_remotes_a">REMOTES<a id="REMOTES"></a></h2>
<div class="sectionbody">
-<div class="para"><p>The name of one of the following can be used instead
+<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>
-<div class="ilist"><ul>
+<div class="ulist"><ul>
<li>
<p>
a remote in the git configuration file: <tt>$GIT_DIR/config</tt>,
@@ -787,10 +881,10 @@ a file in the <tt>$GIT_DIR/branches</tt> directory. </p>
</li>
</ul></div>
-<div class="para"><p>All of these also allow you to omit the refspec from the command line
+<div class="paragraph"><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
+<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
this remote will be used to access the repository. The refspec
@@ -805,10 +899,10 @@ config file would appear like this:</p></div> push = <refspec>
fetch = <refspec></tt></pre>
</div></div>
-<div class="para"><p>The <tt><pushurl></tt> is used for pushes only. It is optional and defaults
+<div class="paragraph"><p>The <tt><pushurl></tt> is used for pushes only. It is optional and defaults
to <tt><url></tt>.</p></div>
<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
+<div class="paragraph"><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
@@ -818,15 +912,14 @@ following format:</p></div> <div class="content">
<pre><tt> URL: one of the above URL format
Push: <refspec>
- Pull: <refspec>
-</tt></pre>
+ Pull: <refspec></tt></pre>
</div></div>
-<div class="para"><p><tt>Push:</tt> lines are used by <em>git push</em> and
+<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
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
+<div class="paragraph"><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></div>
@@ -834,17 +927,17 @@ This file should have the following format:</p></div> <div class="content">
<pre><tt> <url>#<head></tt></pre>
</div></div>
-<div class="para"><p><tt><url></tt> is required; <tt>#<head></tt> is optional.</p></div>
-<div class="para"><p>Depending on the operation, git will use one of the following
-refspecs, if you don't provide one on the command line.
+<div class="paragraph"><p><tt><url></tt> is required; <tt>#<head></tt> 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>
-<div class="para"><p>git fetch uses:</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>
</div></div>
-<div class="para"><p>git push uses:</p></div>
+<div class="paragraph"><p>git push uses:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt> HEAD:refs/heads/<head></tt></pre>
@@ -852,7 +945,7 @@ refspecs, if you don't provide one on the command line. </div>
<h2 id="_examples">EXAMPLES</h2>
<div class="sectionbody">
-<div class="ilist"><ul>
+<div class="ulist"><ul>
<li>
<p>
Update the remote-tracking branches:
@@ -861,7 +954,7 @@ Update the remote-tracking branches: <div class="content">
<pre><tt>$ git fetch origin</tt></pre>
</div></div>
-<div class="para"><p>The above command copies all branches from the remote refs/heads/
+<div class="paragraph"><p>The above command copies all branches from the remote refs/heads/
namespace and stores them to the local refs/remotes/origin/ namespace,
unless the branch.<name>.fetch option is used to specify a non-default
refspec.</p></div>
@@ -874,34 +967,34 @@ Using refspecs explicitly: <div class="content">
<pre><tt>$ git fetch origin +pu:pu maint:tmp</tt></pre>
</div></div>
-<div class="para"><p>This updates (or creates, as necessary) branches <tt>pu</tt> and <tt>tmp</tt> in
+<div class="paragraph"><p>This updates (or creates, as necessary) branches <tt>pu</tt> and <tt>tmp</tt> in
the local repository by fetching from the branches (respectively)
<tt>pu</tt> and <tt>maint</tt> from the remote repository.</p></div>
-<div class="para"><p>The <tt>pu</tt> branch will be updated even if it is does not fast-forward,
+<div class="paragraph"><p>The <tt>pu</tt> branch will be updated even if it is does not fast-forward,
because it is prefixed with a plus sign; <tt>tmp</tt> will not be.</p></div>
</li>
</ul></div>
</div>
<h2 id="_see_also">SEE ALSO</h2>
<div class="sectionbody">
-<div class="para"><p><a href="git-pull.html">git-pull(1)</a></p></div>
+<div class="paragraph"><p><a href="git-pull.html">git-pull(1)</a></p></div>
</div>
<h2 id="_author">Author</h2>
<div class="sectionbody">
-<div class="para"><p>Written by Linus Torvalds <torvalds@osdl.org> and
-Junio C Hamano <gitster@pobox.com></p></div>
+<div class="paragraph"><p>Written by Linus Torvalds <<a href="mailto:torvalds@osdl.org">torvalds@osdl.org</a>> and
+Junio C Hamano <<a href="mailto:gitster@pobox.com">gitster@pobox.com</a>></p></div>
</div>
<h2 id="_documentation">Documentation</h2>
<div class="sectionbody">
-<div class="para"><p>Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.</p></div>
+<div class="paragraph"><p>Documentation by David Greaves, Junio C Hamano and the git-list <<a href="mailto:git@vger.kernel.org">git@vger.kernel.org</a>>.</p></div>
</div>
<h2 id="_git">GIT</h2>
<div class="sectionbody">
-<div class="para"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
+<div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
</div>
<div id="footer">
<div id="footer-text">
-Last updated 2010-10-22 04:11:06 UTC
+Last updated 2010-11-06 00:41:57 UTC
</div>
</div>
</body>
|