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-pull(1)</title>
\r
264 git-pull(1) Manual Page
\r
267 <div class="sectionbody">
\r
269 Pull and merge from another repository
\r
274 <div class="sectionbody">
\r
275 <p><em>git-pull</em> <options> <repository> <refspec>…</p>
\r
277 <h2>DESCRIPTION</h2>
\r
278 <div class="sectionbody">
\r
279 <p>Runs <tt>git-fetch</tt> with the given parameters, and calls <tt>git-merge</tt>
\r
280 to merge the retrieved head(s) into the current branch.</p>
\r
281 <p>Note that you can use <tt>.</tt> (current directory) as the
\r
282 <repository> to pull from the local repository — this is useful
\r
283 when merging local branches into the current branch.</p>
\r
286 <div class="sectionbody">
\r
293 Do not show diffstat at the end of the merge.
\r
301 Perform the merge but pretend the merge failed and do
\r
302 not autocommit, to give the user a chance to inspect and
\r
303 further tweak the merge result before committing.
\r
307 -s <strategy>, --strategy=<strategy>
\r
311 Use the given merge strategy; can be supplied more than
\r
312 once to specify them in the order they should be tried.
\r
313 If there is no <tt>-s</tt> option, a built-in list of strategies
\r
314 is used instead (<tt>git-merge-recursive</tt> when merging a single
\r
315 head, <tt>git-merge-octopus</tt> otherwise).
\r
323 Append ref names and object names of fetched refs to the
\r
324 existing contents of <tt>.git/FETCH_HEAD</tt>. Without this
\r
325 option old data in <tt>.git/FETCH_HEAD</tt> will be overwritten.
\r
329 --upload-pack <upload-pack>
\r
333 When given, and the repository to fetch from is handled
\r
334 by <em>git-fetch-pack</em>, <em>--exec=<upload-pack></em> is passed to
\r
335 the command to specify non-default path for the command
\r
336 run on the other end.
\r
344 When <tt>git-fetch</tt> is used with <tt><rbranch>:<lbranch></tt>
\r
345 refspec, it refuses to update the local branch
\r
346 <tt><lbranch></tt> unless the remote branch <tt><rbranch></tt> it
\r
347 fetches is a descendant of <tt><lbranch></tt>. This option
\r
348 overrides that check.
\r
356 By default, <tt>git-fetch</tt> fetches tags that point at
\r
357 objects that are downloaded from the remote repository
\r
358 and stores them locally. This option disables this
\r
359 automatic tag following.
\r
367 Most of the tags are fetched automatically as branch
\r
368 heads are downloaded, but tags that do not point at
\r
369 objects reachable from the branch heads that are being
\r
370 tracked will not be fetched by this mechanism. This
\r
371 flag lets all tags and their associated objects be
\r
380 Keep downloaded pack.
\r
384 -u, --update-head-ok
\r
388 By default <tt>git-fetch</tt> refuses to update the head which
\r
389 corresponds to the current branch. This flag disables the
\r
390 check. Note that fetching into the current branch will not
\r
391 update the index and working directory, so use it with care.
\r
399 The "remote" repository that is the source of a fetch
\r
400 or pull operation. See the section <a href="#URLS">GIT URLS</a> below.
\r
408 The canonical format of a <refspec> parameter is
\r
409 <tt>+?<src>:<dst></tt>; that is, an optional plus <tt>+</tt>, followed
\r
410 by the source ref, followed by a colon <tt>:</tt>, followed by
\r
411 the destination ref.
\r
413 <p>The remote ref that matches <src>
\r
414 is fetched, and if <dst> is not empty string, the local
\r
415 ref that matches it is fast forwarded using <src>.
\r
416 Again, if the optional plus <tt>+</tt> is used, the local ref
\r
417 is updated even if it does not result in a fast forward
\r
419 <div class="admonitionblock">
\r
422 <div class="title">Note</div>
\r
424 <td class="content">If the remote branch from which you want to pull is
\r
425 modified in non-linear ways such as being rewound and
\r
426 rebased frequently, then a pull will attempt a merge with
\r
427 an older version of itself, likely conflict, and fail.
\r
428 It is under these conditions that you would want to use
\r
429 the <tt>+</tt> sign to indicate non-fast-forward updates will
\r
430 be needed. There is currently no easy way to determine
\r
431 or declare that a branch will be made available in a
\r
432 repository with this behavior; the pulling user simply
\r
433 must know this is the expected usage pattern for a branch.</td>
\r
436 <div class="admonitionblock">
\r
439 <div class="title">Note</div>
\r
441 <td class="content">You never do your own development on branches that appear
\r
442 on the right hand side of a <refspec> colon on <tt>Pull:</tt> lines;
\r
443 they are to be updated by <tt>git-fetch</tt>. If you intend to do
\r
444 development derived from a remote branch <tt>B</tt>, have a <tt>Pull:</tt>
\r
445 line to track it (i.e. <tt>Pull: B:remote-B</tt>), and have a separate
\r
446 branch <tt>my-B</tt> to do your development on top of it. The latter
\r
447 is created by <tt>git branch my-B remote-B</tt> (or its equivalent <tt>git
\r
448 checkout -b my-B remote-B</tt>). Run <tt>git fetch</tt> to keep track of
\r
449 the progress of the remote side, and when you see something new
\r
450 on the remote branch, merge it into your development branch with
\r
451 <tt>git pull . remote-B</tt>, while you are on <tt>my-B</tt> branch.
\r
452 The common <tt>Pull: master:origin</tt> mapping of a remote <tt>master</tt>
\r
453 branch to a local <tt>origin</tt> branch, which is then merged to a
\r
454 local development branch, again typically named <tt>master</tt>, is made
\r
455 when you run <tt>git clone</tt> for you to follow this pattern.</td>
\r
458 <div class="admonitionblock">
\r
461 <div class="title">Note</div>
\r
463 <td class="content">There is a difference between listing multiple <refspec>
\r
464 directly on <tt>git-pull</tt> command line and having multiple
\r
465 <tt>Pull:</tt> <refspec> lines for a <repository> and running
\r
466 <tt>git-pull</tt> command without any explicit <refspec> parameters.
\r
467 <refspec> listed explicitly on the command line are always
\r
468 merged into the current branch after fetching. In other words,
\r
469 if you list more than one remote refs, you would be making
\r
470 an Octopus. While <tt>git-pull</tt> run without any explicit <refspec>
\r
471 parameter takes default <refspec>s from <tt>Pull:</tt> lines, it
\r
472 merges only the first <refspec> found into the current branch,
\r
473 after fetching all the remote refs. This is because making an
\r
474 Octopus from remote refs is rarely done, while keeping track
\r
475 of multiple remote heads in one-go by fetching more than one
\r
476 is often useful.</td>
\r
479 <p>Some short-cut notations are also supported.</p>
\r
483 <tt>tag <tag></tt> means the same as <tt>refs/tags/<tag>:refs/tags/<tag></tt>;
\r
484 it requests fetching everything up to the given tag.
\r
489 A parameter <ref> without a colon is equivalent to
\r
490 <ref>: when pulling/fetching, so it merges <ref> into the current
\r
491 branch without storing the remote branch anywhere locally
\r
498 <h2>GIT URLS<a id="URLS"></a></h2>
\r
499 <div class="sectionbody">
\r
500 <p>One of the following notations can be used
\r
501 to name the remote repository:</p>
\r
502 <div class="exampleblock">
\r
503 <div class="exampleblock-content">
\r
507 rsync://host.xz/path/to/repo.git/
\r
512 http://host.xz/path/to/repo.git/
\r
517 https://host.xz/path/to/repo.git/
\r
522 git://host.xz/path/to/repo.git/
\r
527 git://host.xz/~user/path/to/repo.git/
\r
532 ssh://host.xz/path/to/repo.git/
\r
537 ssh://host.xz/~user/path/to/repo.git/
\r
542 ssh://host.xz/~/path/to/repo.git
\r
547 <p>SSH Is the default transport protocol and also supports an
\r
548 scp-like syntax. Both syntaxes support username expansion,
\r
549 as does the native git protocol. The following three are
\r
550 identical to the last three above, respectively:</p>
\r
551 <div class="exampleblock">
\r
552 <div class="exampleblock-content">
\r
556 host.xz:/path/to/repo.git/
\r
561 host.xz:~user/path/to/repo.git/
\r
566 host.xz:path/to/repo.git
\r
571 <p>To sync with a local directory, use:</p>
\r
572 <div class="exampleblock">
\r
573 <div class="exampleblock-content">
\r
584 <div class="sectionbody">
\r
585 <p>In addition to the above, as a short-hand, the name of a
\r
586 file in <tt>$GIT_DIR/remotes</tt> directory can be given; the
\r
587 named file should be in the following format:</p>
\r
588 <div class="literalblock">
\r
589 <div class="content">
\r
590 <pre><tt>URL: one of the above URL format
\r
591 Push: <refspec>
\r
592 Pull: <refspec></tt></pre>
\r
594 <p>Then such a short-hand is specified in place of
\r
595 <repository> without <refspec> parameters on the command
\r
596 line, <refspec> specified on <tt>Push:</tt> lines or <tt>Pull:</tt>
\r
597 lines are used for <tt>git-push</tt> and <tt>git-fetch</tt>/<tt>git-pull</tt>,
\r
598 respectively. Multiple <tt>Push:</tt> and and <tt>Pull:</tt> lines may
\r
599 be specified for additional branch mappings.</p>
\r
600 <p>The name of a file in <tt>$GIT_DIR/branches</tt> directory can be
\r
601 specified as an older notation short-hand; the named
\r
602 file should contain a single line, a URL in one of the
\r
603 above formats, optionally followed by a hash <tt>#</tt> and the
\r
604 name of remote head (URL fragment notation).
\r
605 <tt>$GIT_DIR/branches/<remote></tt> file that stores a <url>
\r
606 without the fragment is equivalent to have this in the
\r
607 corresponding file in the <tt>$GIT_DIR/remotes/</tt> directory.</p>
\r
608 <div class="literalblock">
\r
609 <div class="content">
\r
610 <pre><tt>URL: <url>
\r
611 Pull: refs/heads/master:<remote></tt></pre>
\r
613 <p>while having <tt><url>#<head></tt> is equivalent to</p>
\r
614 <div class="literalblock">
\r
615 <div class="content">
\r
616 <pre><tt>URL: <url>
\r
617 Pull: refs/heads/<head>:<remote></tt></pre>
\r
620 <h2>MERGE STRATEGIES</h2>
\r
621 <div class="sectionbody">
\r
628 This can only resolve two heads (i.e. the current branch
\r
629 and another branch you pulled from) using 3-way merge
\r
630 algorithm. It tries to carefully detect criss-cross
\r
631 merge ambiguities and is considered generally safe and
\r
640 This can only resolve two heads using 3-way merge
\r
641 algorithm. When there are more than one common
\r
642 ancestors that can be used for 3-way merge, it creates a
\r
643 merged tree of the common ancestors and uses that as
\r
644 the reference tree for the 3-way merge. This has been
\r
645 reported to result in fewer merge conflicts without
\r
646 causing mis-merges by tests done on actual merge commits
\r
647 taken from Linux 2.6 kernel development history.
\r
648 Additionally this can detect and handle merges involving
\r
649 renames. This is the default merge strategy when
\r
650 pulling or merging one branch.
\r
658 This resolves more than two-head case, but refuses to do
\r
659 complex merge that needs manual resolution. It is
\r
660 primarily meant to be used for bundling topic branch
\r
661 heads together. This is the default merge strategy when
\r
662 pulling or merging more than one branches.
\r
670 This resolves any number of heads, but the result of the
\r
671 merge is always the current branch head. It is meant to
\r
672 be used to supersede old development history of side
\r
679 <div class="sectionbody">
\r
682 git pull, git pull origin
\r
686 Fetch the default head from the repository you cloned
\r
687 from and merge it into your current branch.
\r
691 git pull -s ours . obsolete
\r
695 Merge local branch <tt>obsolete</tt> into the current branch,
\r
696 using <tt>ours</tt> merge strategy.
\r
700 git pull . fixes enhancements
\r
704 Bundle local branch <tt>fixes</tt> and <tt>enhancements</tt> on top of
\r
705 the current branch, making an Octopus merge.
\r
709 git pull --no-commit . maint
\r
713 Merge local branch <tt>maint</tt> into the current branch, but
\r
714 do not make a commit automatically. This can be used
\r
715 when you want to include further changes to the merge,
\r
716 or want to write your own merge commit message.
\r
718 <p>You should refrain from abusing this option to sneak substantial
\r
719 changes into a merge commit. Small fixups like bumping
\r
720 release/version name would be acceptable.</p>
\r
723 Command line pull of multiple branches from one repository
\r
726 <div class="listingblock">
\r
727 <div class="content">
\r
728 <pre><tt>$ cat .git/remotes/origin
\r
729 URL: git://git.kernel.org/pub/scm/git/git.git
\r
730 Pull: master:origin
\r
732 $ git checkout master
\r
733 $ git fetch origin master:origin +pu:pu maint:maint
\r
734 $ git pull . origin</tt></pre>
\r
736 <p>Here, a typical <tt>.git/remotes/origin</tt> file from a
\r
737 <tt>git-clone</tt> operation is used in combination with
\r
738 command line options to <tt>git-fetch</tt> to first update
\r
739 multiple branches of the local repository and then
\r
740 to merge the remote <tt>origin</tt> branch into the local
\r
741 <tt>master</tt> branch. The local <tt>pu</tt> branch is updated
\r
742 even if it does not result in a fast forward update.
\r
743 Here, the pull can obtain its objects from the local
\r
744 repository using <tt>.</tt>, as the previous <tt>git-fetch</tt> is
\r
745 known to have already obtained and made available
\r
746 all the necessary objects.</p>
\r
749 Pull of multiple branches from one repository using <tt>.git/remotes</tt> file
\r
752 <div class="listingblock">
\r
753 <div class="content">
\r
754 <pre><tt>$ cat .git/remotes/origin
\r
755 URL: git://git.kernel.org/pub/scm/git/git.git
\r
756 Pull: master:origin
\r
760 $ git checkout master
\r
761 $ git pull origin</tt></pre>
\r
763 <p>Here, a typical <tt>.git/remotes/origin</tt> file from a
\r
764 <tt>git-clone</tt> operation has been hand-modified to include
\r
765 the branch-mapping of additional remote and local
\r
766 heads directly. A single <tt>git-pull</tt> operation while
\r
767 in the <tt>master</tt> branch will fetch multiple heads and
\r
768 merge the remote <tt>origin</tt> head into the current,
\r
769 local <tt>master</tt> branch.</p>
\r
772 <p>If you tried a pull which resulted in a complex conflicts and
\r
773 would want to start over, you can recover with
\r
774 <a href="git-reset.html">git-reset(1)</a>.</p>
\r
777 <div class="sectionbody">
\r
778 <p><a href="git-fetch.html">git-fetch(1)</a>, <a href="git-merge.html">git-merge(1)</a></p>
\r
781 <div class="sectionbody">
\r
782 <p>Written by Linus Torvalds <torvalds@osdl.org>
\r
783 and Junio C Hamano <junkio@cox.net></p>
\r
785 <h2>Documentation</h2>
\r
786 <div class="sectionbody">
\r
787 <p>Documentation by Jon Loeliger,
\r
789 Junio C Hamano and the git-list <git@vger.kernel.org>.</p>
\r
792 <div class="sectionbody">
\r
793 <p>Part of the <a href="git.html">git(7)</a> suite</p>
\r
796 <div id="footer-text">
\r
797 Last updated 10-Mar-2006 00:31:31 UTC
\r