1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
\r
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
\r
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
\r
5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
\r
6 <meta name="generator" content="AsciiDoc 7.0.2" />
\r
7 <style type="text/css">
\r
9 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
\r
11 border: 1px solid red;
\r
16 margin: 1em 5% 1em 5%;
\r
20 a:visited { color: fuchsia; }
\r
34 h1, h2, h3, h4, h5, h6 {
\r
36 font-family: sans-serif;
\r
38 margin-bottom: 0.5em;
\r
43 border-bottom: 2px solid silver;
\r
46 border-bottom: 2px solid silver;
\r
56 border: 1px solid silver;
\r
61 margin-bottom: 0.5em;
\r
71 font-family: sans-serif;
\r
78 font-family: sans-serif;
\r
82 font-family: sans-serif;
\r
84 border-top: 2px solid silver;
\r
90 padding-bottom: 0.5em;
\r
94 padding-bottom: 0.5em;
\r
98 div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
\r
99 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
\r
100 div.admonitionblock {
\r
103 margin-bottom: 1.5em;
\r
105 div.admonitionblock {
\r
107 margin-bottom: 2.5em;
\r
110 div.content { /* Block element content. */
\r
114 /* Block element titles. */
\r
115 div.title, caption.title {
\r
116 font-family: sans-serif;
\r
120 margin-bottom: 0.5em;
\r
126 td div.title:first-child {
\r
129 div.content div.title:first-child {
\r
132 div.content + div.title {
\r
136 div.sidebarblock > div.content {
\r
137 background: #ffffee;
\r
138 border: 1px solid silver;
\r
142 div.listingblock > div.content {
\r
143 border: 1px solid silver;
\r
144 background: #f4f4f4;
\r
148 div.quoteblock > div.content {
\r
149 padding-left: 2.0em;
\r
151 div.quoteblock .attribution {
\r
155 div.admonitionblock .icon {
\r
156 vertical-align: top;
\r
159 text-decoration: underline;
\r
161 padding-right: 0.5em;
\r
163 div.admonitionblock td.content {
\r
164 padding-left: 0.5em;
\r
165 border-left: 2px solid silver;
\r
168 div.exampleblock > div.content {
\r
169 border-left: 2px solid silver;
\r
173 div.verseblock div.content {
\r
177 div.imageblock div.content { padding-left: 0; }
\r
178 div.imageblock img { border: 1px solid silver; }
\r
179 span.image img { border-style: none; }
\r
183 margin-bottom: 0.8em;
\r
188 font-style: italic;
\r
190 dd > *:first-child {
\r
195 list-style-position: outside;
\r
198 list-style-type: lower-alpha;
\r
201 div.tableblock > table {
\r
202 border-color: #527bbd;
\r
206 font-family: sans-serif;
\r
215 margin-bottom: 0.8em;
\r
218 vertical-align: top;
\r
219 font-style: italic;
\r
220 padding-right: 0.8em;
\r
223 vertical-align: top;
\r
227 div#footer-badges { display: none; }
\r
229 include::./stylesheets/xhtml11-manpage.css[]
\r
230 /* Workarounds for IE6's broken and incomplete CSS2. */
\r
232 div.sidebar-content {
\r
233 background: #ffffee;
\r
234 border: 1px solid silver;
\r
237 div.sidebar-title, div.image-title {
\r
238 font-family: sans-serif;
\r
241 margin-bottom: 0.5em;
\r
244 div.listingblock div.content {
\r
245 border: 1px solid silver;
\r
246 background: #f4f4f4;
\r
250 div.quoteblock-content {
\r
251 padding-left: 2.0em;
\r
254 div.exampleblock-content {
\r
255 border-left: 2px solid silver;
\r
256 padding-left: 0.5em;
\r
259 <title>git-fetch(1)</title>
\r
264 git-fetch(1) Manual Page
\r
267 <div class="sectionbody">
\r
269 Download objects and a head from another repository
\r
274 <div class="sectionbody">
\r
275 <p><em>git-fetch</em> <options> <repository> <refspec>…</p>
\r
277 <h2>DESCRIPTION</h2>
\r
278 <div class="sectionbody">
\r
279 <p>Fetches named heads or tags from another repository, along with
\r
280 the objects necessary to complete them.</p>
\r
281 <p>The ref names and their object names of fetched refs are stored
\r
282 in <tt>.git/FETCH_HEAD</tt>. This information is left for a later merge
\r
283 operation done by "git merge".</p>
\r
286 <div class="sectionbody">
\r
293 Append ref names and object names of fetched refs to the
\r
294 existing contents of <tt>.git/FETCH_HEAD</tt>. Without this
\r
295 option old data in <tt>.git/FETCH_HEAD</tt> will be overwritten.
\r
299 --upload-pack <upload-pack>
\r
303 When given, and the repository to fetch from is handled
\r
304 by <em>git-fetch-pack</em>, <em>--exec=<upload-pack></em> is passed to
\r
305 the command to specify non-default path for the command
\r
306 run on the other end.
\r
314 When <tt>git-fetch</tt> is used with <tt><rbranch>:<lbranch></tt>
\r
315 refspec, it refuses to update the local branch
\r
316 <tt><lbranch></tt> unless the remote branch <tt><rbranch></tt> it
\r
317 fetches is a descendant of <tt><lbranch></tt>. This option
\r
318 overrides that check.
\r
326 By default, <tt>git-fetch</tt> fetches tags that point at
\r
327 objects that are downloaded from the remote repository
\r
328 and stores them locally. This option disables this
\r
329 automatic tag following.
\r
337 Most of the tags are fetched automatically as branch
\r
338 heads are downloaded, but tags that do not point at
\r
339 objects reachable from the branch heads that are being
\r
340 tracked will not be fetched by this mechanism. This
\r
341 flag lets all tags and their associated objects be
\r
350 Keep downloaded pack.
\r
354 -u, --update-head-ok
\r
358 By default <tt>git-fetch</tt> refuses to update the head which
\r
359 corresponds to the current branch. This flag disables the
\r
360 check. Note that fetching into the current branch will not
\r
361 update the index and working directory, so use it with care.
\r
369 The "remote" repository that is the source of a fetch
\r
370 or pull operation. See the section <a href="#URLS">GIT URLS</a> below.
\r
378 The canonical format of a <refspec> parameter is
\r
379 <tt>+?<src>:<dst></tt>; that is, an optional plus <tt>+</tt>, followed
\r
380 by the source ref, followed by a colon <tt>:</tt>, followed by
\r
381 the destination ref.
\r
383 <p>The remote ref that matches <src>
\r
384 is fetched, and if <dst> is not empty string, the local
\r
385 ref that matches it is fast forwarded using <src>.
\r
386 Again, if the optional plus <tt>+</tt> is used, the local ref
\r
387 is updated even if it does not result in a fast forward
\r
389 <div class="admonitionblock">
\r
392 <div class="title">Note</div>
\r
394 <td class="content">If the remote branch from which you want to pull is
\r
395 modified in non-linear ways such as being rewound and
\r
396 rebased frequently, then a pull will attempt a merge with
\r
397 an older version of itself, likely conflict, and fail.
\r
398 It is under these conditions that you would want to use
\r
399 the <tt>+</tt> sign to indicate non-fast-forward updates will
\r
400 be needed. There is currently no easy way to determine
\r
401 or declare that a branch will be made available in a
\r
402 repository with this behavior; the pulling user simply
\r
403 must know this is the expected usage pattern for a branch.</td>
\r
406 <div class="admonitionblock">
\r
409 <div class="title">Note</div>
\r
411 <td class="content">You never do your own development on branches that appear
\r
412 on the right hand side of a <refspec> colon on <tt>Pull:</tt> lines;
\r
413 they are to be updated by <tt>git-fetch</tt>. If you intend to do
\r
414 development derived from a remote branch <tt>B</tt>, have a <tt>Pull:</tt>
\r
415 line to track it (i.e. <tt>Pull: B:remote-B</tt>), and have a separate
\r
416 branch <tt>my-B</tt> to do your development on top of it. The latter
\r
417 is created by <tt>git branch my-B remote-B</tt> (or its equivalent <tt>git
\r
418 checkout -b my-B remote-B</tt>). Run <tt>git fetch</tt> to keep track of
\r
419 the progress of the remote side, and when you see something new
\r
420 on the remote branch, merge it into your development branch with
\r
421 <tt>git pull . remote-B</tt>, while you are on <tt>my-B</tt> branch.
\r
422 The common <tt>Pull: master:origin</tt> mapping of a remote <tt>master</tt>
\r
423 branch to a local <tt>origin</tt> branch, which is then merged to a
\r
424 local development branch, again typically named <tt>master</tt>, is made
\r
425 when you run <tt>git clone</tt> for you to follow this pattern.</td>
\r
428 <div class="admonitionblock">
\r
431 <div class="title">Note</div>
\r
433 <td class="content">There is a difference between listing multiple <refspec>
\r
434 directly on <tt>git-pull</tt> command line and having multiple
\r
435 <tt>Pull:</tt> <refspec> lines for a <repository> and running
\r
436 <tt>git-pull</tt> command without any explicit <refspec> parameters.
\r
437 <refspec> listed explicitly on the command line are always
\r
438 merged into the current branch after fetching. In other words,
\r
439 if you list more than one remote refs, you would be making
\r
440 an Octopus. While <tt>git-pull</tt> run without any explicit <refspec>
\r
441 parameter takes default <refspec>s from <tt>Pull:</tt> lines, it
\r
442 merges only the first <refspec> found into the current branch,
\r
443 after fetching all the remote refs. This is because making an
\r
444 Octopus from remote refs is rarely done, while keeping track
\r
445 of multiple remote heads in one-go by fetching more than one
\r
446 is often useful.</td>
\r
449 <p>Some short-cut notations are also supported.</p>
\r
453 <tt>tag <tag></tt> means the same as <tt>refs/tags/<tag>:refs/tags/<tag></tt>;
\r
454 it requests fetching everything up to the given tag.
\r
459 A parameter <ref> without a colon is equivalent to
\r
460 <ref>: when pulling/fetching, so it merges <ref> into the current
\r
461 branch without storing the remote branch anywhere locally
\r
468 <h2>GIT URLS<a id="URLS"></a></h2>
\r
469 <div class="sectionbody">
\r
470 <p>One of the following notations can be used
\r
471 to name the remote repository:</p>
\r
472 <div class="exampleblock">
\r
473 <div class="exampleblock-content">
\r
477 rsync://host.xz/path/to/repo.git/
\r
482 http://host.xz/path/to/repo.git/
\r
487 https://host.xz/path/to/repo.git/
\r
492 git://host.xz/path/to/repo.git/
\r
497 git://host.xz/~user/path/to/repo.git/
\r
502 ssh://host.xz/path/to/repo.git/
\r
507 ssh://host.xz/~user/path/to/repo.git/
\r
512 ssh://host.xz/~/path/to/repo.git
\r
517 <p>SSH Is the default transport protocol and also supports an
\r
518 scp-like syntax. Both syntaxes support username expansion,
\r
519 as does the native git protocol. The following three are
\r
520 identical to the last three above, respectively:</p>
\r
521 <div class="exampleblock">
\r
522 <div class="exampleblock-content">
\r
526 host.xz:/path/to/repo.git/
\r
531 host.xz:~user/path/to/repo.git/
\r
536 host.xz:path/to/repo.git
\r
541 <p>To sync with a local directory, use:</p>
\r
542 <div class="exampleblock">
\r
543 <div class="exampleblock-content">
\r
554 <div class="sectionbody">
\r
555 <p>In addition to the above, as a short-hand, the name of a
\r
556 file in <tt>$GIT_DIR/remotes</tt> directory can be given; the
\r
557 named file should be in the following format:</p>
\r
558 <div class="literalblock">
\r
559 <div class="content">
\r
560 <pre><tt>URL: one of the above URL format
\r
561 Push: <refspec>
\r
562 Pull: <refspec></tt></pre>
\r
564 <p>Then such a short-hand is specified in place of
\r
565 <repository> without <refspec> parameters on the command
\r
566 line, <refspec> specified on <tt>Push:</tt> lines or <tt>Pull:</tt>
\r
567 lines are used for <tt>git-push</tt> and <tt>git-fetch</tt>/<tt>git-pull</tt>,
\r
568 respectively. Multiple <tt>Push:</tt> and and <tt>Pull:</tt> lines may
\r
569 be specified for additional branch mappings.</p>
\r
570 <p>The name of a file in <tt>$GIT_DIR/branches</tt> directory can be
\r
571 specified as an older notation short-hand; the named
\r
572 file should contain a single line, a URL in one of the
\r
573 above formats, optionally followed by a hash <tt>#</tt> and the
\r
574 name of remote head (URL fragment notation).
\r
575 <tt>$GIT_DIR/branches/<remote></tt> file that stores a <url>
\r
576 without the fragment is equivalent to have this in the
\r
577 corresponding file in the <tt>$GIT_DIR/remotes/</tt> directory.</p>
\r
578 <div class="literalblock">
\r
579 <div class="content">
\r
580 <pre><tt>URL: <url>
\r
581 Pull: refs/heads/master:<remote></tt></pre>
\r
583 <p>while having <tt><url>#<head></tt> is equivalent to</p>
\r
584 <div class="literalblock">
\r
585 <div class="content">
\r
586 <pre><tt>URL: <url>
\r
587 Pull: refs/heads/<head>:<remote></tt></pre>
\r
591 <div class="sectionbody">
\r
592 <p><a href="git-pull.html">git-pull(1)</a></p>
\r
595 <div class="sectionbody">
\r
596 <p>Written by Linus Torvalds <torvalds@osdl.org> and
\r
597 Junio C Hamano <junkio@cox.net></p>
\r
599 <h2>Documentation</h2>
\r
600 <div class="sectionbody">
\r
601 <p>Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.</p>
\r
604 <div class="sectionbody">
\r
605 <p>Part of the <a href="git.html">git(7)</a> suite</p>
\r
608 <div id="footer-text">
\r
609 Last updated 10-Mar-2006 00:31:25 UTC
\r