| blob | 2f78043d4ff5506b3ebadf8eab7991a6524e16b6 |
4 <head>
9 /* Debug borders */
11 /*
12 border: 1px solid red;
13 */
14 }
16 body {
18 }
20 a {
23 }
26 }
28 em {
31 }
33 strong {
36 }
38 tt {
40 }
48 }
52 }
53 h2 {
55 }
56 h3 {
58 }
59 h3 + * {
61 }
66 }
68 hr {
70 }
72 p {
75 }
79 }
81 pre {
84 }
86 span#author {
91 }
92 span#email {
93 }
96 }
98 div#footer {
104 }
105 div#footer-text {
108 }
109 div#footer-badges {
112 }
114 div#preamble {
117 }
123 }
127 }
131 }
133 /* Block element titles. */
141 }
144 }
148 }
151 }
154 }
160 }
166 }
171 }
175 }
180 }
183 }
187 }
188 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
191 }
200 }
204 }
209 }
215 dl {
218 }
219 dt {
224 }
227 }
231 }
234 }
237 }
240 }
243 }
246 }
253 }
257 }
258 thead {
261 }
262 tfoot {
264 }
267 }
270 }
271 /* Because the table frame attribute is overriden by CSS in most browsers. */
274 }
278 }
282 }
288 }
291 }
294 }
300 }
303 }
307 }
311 }
315 }
317 div#toctitle {
324 }
329 }
333 }
337 }
341 }
342 /* Overrides for manpage documents */
343 h1 {
348 }
349 h2 {
351 }
354 }
358 }
360 /* Workarounds for IE6's broken and incomplete CSS2. */
366 }
373 }
379 }
384 }
388 }
392 }
397 }
399 /* IE6 sets dynamically generated links as visited. */
401 </style>
402 </head>
403 <body>
405 <h1>
406 git-fetch(1) Manual Page
407 </h1>
410 <p>git-fetch -
411 Download objects and refs from another repository
412 </p>
413 </div>
414 </div>
417 <div class="paragraph"><p><em>git fetch</em> [<options>] [<repository> [<refspec>…]]</p></div>
419 <div class="paragraph"><p><em>git fetch</em> --multiple [<options>] [(<repository> | <group>)…]</p></div>
421 </div>
425 along with the objects necessary to complete them.</p></div>
429 <div class="paragraph"><p>When <refspec> stores the fetched result in remote-tracking branches,
430 the tags that point at these branches are automatically
431 followed. This is done by first fetching from the remote using
433 pointed by remote tags that it does not yet have, then fetch
434 those missing tags. If the other end has tags that point at
435 branches you are not interested in, you will not get them.</p></div>
436 <div class="paragraph"><p><em>git fetch</em> can fetch from either a single named repository, or
440 </div>
445 --all
446 </dt>
447 <dd>
448 <p>
449 Fetch all remotes.
450 </p>
451 </dd>
453 -a
454 </dt>
456 --append
457 </dt>
458 <dd>
459 <p>
460 Append ref names and object names of fetched refs to the
463 </p>
464 </dd>
467 </dt>
468 <dd>
469 <p>
471 <tt>git clone</tt> with <tt>--depth=<depth></tt> option (see <a href="git-clone.html">git-clone(1)</a>)
472 by the specified number of commits.
473 </p>
474 </dd>
476 --dry-run
477 </dt>
478 <dd>
479 <p>
480 Show what would be done, without making any changes.
481 </p>
482 </dd>
484 -f
485 </dt>
487 --force
488 </dt>
489 <dd>
490 <p>
492 refspec, it refuses to update the local branch
495 overrides that check.
496 </p>
497 </dd>
499 -k
500 </dt>
502 --keep
503 </dt>
504 <dd>
505 <p>
506 Keep downloaded pack.
507 </p>
508 </dd>
510 --multiple
511 </dt>
512 <dd>
513 <p>
516 </p>
517 </dd>
519 -p
520 </dt>
522 --prune
523 </dt>
524 <dd>
525 <p>
526 After fetching, remove any remote-tracking branches which
527 no longer exist on the remote.
528 </p>
529 </dd>
531 -n
532 </dt>
534 --no-tags
535 </dt>
536 <dd>
537 <p>
538 By default, tags that point at objects that are downloaded
539 from the remote repository are fetched and stored locally.
540 This option disables this automatic tag following. The default
543 </p>
544 </dd>
546 -t
547 </dt>
549 --tags
550 </dt>
551 <dd>
552 <p>
553 Most of the tags are fetched automatically as branch
554 heads are downloaded, but tags that do not point at
555 objects reachable from the branch heads that are being
556 tracked will not be fetched by this mechanism. This
557 flag lets all tags and their associated objects be
558 downloaded. The default behavior for a remote may be
561 </p>
562 </dd>
564 --[no-]recurse-submodules
565 </dt>
566 <dd>
567 <p>
568 This option controls if new commits of all populated submodules should
569 be fetched too (see <a href="git-config.html">git-config(1)</a> and <a href="gitmodules.html">gitmodules(5)</a>).
570 </p>
571 </dd>
574 </dt>
575 <dd>
576 <p>
578 such as "Fetching submodule foo". This option is used
579 internally when recursing over submodules.
580 </p>
581 </dd>
583 -u
584 </dt>
586 --update-head-ok
587 </dt>
588 <dd>
589 <p>
591 corresponds to the current branch. This flag disables the
594 implementing your own Porcelain you are not supposed to
595 use it.
596 </p>
597 </dd>
600 </dt>
601 <dd>
602 <p>
603 When given, and the repository to fetch from is handled
605 the command to specify non-default path for the command
606 run on the other end.
607 </p>
608 </dd>
610 -q
611 </dt>
613 --quiet
614 </dt>
615 <dd>
616 <p>
617 Pass --quiet to git-fetch-pack and silence any other internally
618 used git commands. Progress is not reported to the standard error
619 stream.
620 </p>
621 </dd>
623 -v
624 </dt>
626 --verbose
627 </dt>
628 <dd>
629 <p>
630 Be verbose.
631 </p>
632 </dd>
634 --progress
635 </dt>
636 <dd>
637 <p>
638 Progress status is reported on the standard error stream
639 by default when it is attached to a terminal, unless -q
640 is specified. This flag forces progress status even if the
641 standard error stream is not directed to a terminal.
642 </p>
643 </dd>
646 </dt>
647 <dd>
648 <p>
649 The "remote" repository that is the source of a fetch
650 or pull operation. This parameter can be either a URL
653 </p>
654 </dd>
657 </dt>
658 <dd>
659 <p>
660 A name referring to a list of repositories as the value
663 </p>
664 </dd>
667 </dt>
668 <dd>
669 <p>
673 </p>
678 is updated even if it does not result in a fast-forward
679 update.</p></div>
681 <table><tr>
684 </td>
686 modified in non-linear ways such as being rewound and
687 rebased frequently, then a pull will attempt a merge with
688 an older version of itself, likely conflict, and fail.
689 It is under these conditions that you would want to use
691 be needed. There is currently no easy way to determine
692 or declare that a branch will be made available in a
693 repository with this behavior; the pulling user simply
694 must know this is the expected usage pattern for a branch.</td>
695 </tr></table>
696 </div>
698 <table><tr>
701 </td>
710 the progress of the remote side, and when you see something new
711 on the remote branch, merge it into your development branch with
713 </tr></table>
714 </div>
716 <table><tr>
719 </td>
725 merged into the current branch after fetching. In other words,
726 if you list more than one remote refs, you would be making
730 after fetching all the remote refs. This is because making an
731 Octopus from remote refs is rarely done, while keeping track
732 of multiple remote heads in one-go by fetching more than one
733 is often useful.</td>
734 </tr></table>
735 </div>
738 <li>
739 <p>
740 <tt>tag <tag></tt> means the same as <tt>refs/tags/<tag>:refs/tags/<tag></tt>;
741 it requests fetching everything up to the given tag.
742 </p>
743 </li>
744 <li>
745 <p>
748 branch without storing the remote branch anywhere locally
749 </p>
750 </li>
751 </ul></div>
752 </dd>
753 </dl></div>
754 </div>
757 <div class="paragraph"><p>In general, URLs contain information about the transport protocol, the
758 address of the remote server, and the path to the repository.
759 Depending on the transport protocol, some of this information may be
760 absent.</p></div>
762 protocols. The following syntaxes may be used with them:</p></div>
764 <li>
765 <p>
767 </p>
768 </li>
769 <li>
770 <p>
772 </p>
773 </li>
774 <li>
775 <p>
777 </p>
778 </li>
779 <li>
780 <p>
782 </p>
783 </li>
784 <li>
785 <p>
786 rsync://host.xz/path/to/repo.git/
787 </p>
788 </li>
789 </ul></div>
790 <div class="paragraph"><p>An alternative scp-like syntax may also be used with the ssh protocol:</p></div>
792 <li>
793 <p>
795 </p>
796 </li>
797 </ul></div>
798 <div class="paragraph"><p>The ssh and git protocols additionally support ~username expansion:</p></div>
800 <li>
801 <p>
803 </p>
804 </li>
805 <li>
806 <p>
808 </p>
809 </li>
810 <li>
811 <p>
813 </p>
814 </li>
815 </ul></div>
817 syntaxes may be used:</p></div>
819 <li>
820 <p>
821 /path/to/repo.git/
822 </p>
823 </li>
824 <li>
825 <p>
827 </p>
828 </li>
829 </ul></div>
832 details.</p></div>
833 <div class="paragraph"><p>When git doesn’t know how to handle a certain transport protocol, it
835 exists. To explicitly request a remote helper, the following syntax
836 may be used:</p></div>
838 <li>
839 <p>
841 </p>
842 </li>
843 </ul></div>
844 <div class="paragraph"><p>where <address> may be a path, a server and path, or an arbitrary
845 URL-like string recognized by the specific remote helper being
847 <div class="paragraph"><p>If there are a large number of similarly-named remote repositories and
848 you want to use a different format for them (such that the URLs you
849 use will be rewritten into URLs that work), you can create a
850 configuration section of the form:</p></div>
855 </div></div>
860 insteadOf = host.xz:/path/to/
861 insteadOf = work:</tt></pre>
862 </div></div>
863 <div class="paragraph"><p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
866 configuration section of the form:</p></div>
871 </div></div>
876 pushInsteadOf = git://example.org/</tt></pre>
877 </div></div>
879 "ssh://example.org/path/to/repo.git" for pushes, but pulls will still
880 use the original URL.</p></div>
881 </div>
887 <li>
888 <p>
890 </p>
891 </li>
892 <li>
893 <p>
895 </p>
896 </li>
897 <li>
898 <p>
900 </p>
901 </li>
902 </ul></div>
904 because they each contain a refspec which git will use by default.</p></div>
905 <h3 id="_named_remote_in_configuration_file">Named remote in configuration file</h3><div style="clear:left"></div>
906 <div class="paragraph"><p>You can choose to provide the name of a remote which you had previously
907 configured using <a href="git-remote.html">git-remote(1)</a>, <a href="git-config.html">git-config(1)</a>
909 this remote will be used to access the repository. The refspec
910 of this remote will be used by default when you do
911 not provide a refspec on the command line. The entry in the
912 config file would appear like this:</p></div>
920 </div></div>
921 <div class="paragraph"><p>The <tt><pushurl></tt> is used for pushes only. It is optional and defaults
923 <h3 id="_named_file_in_tt_git_dir_remotes_tt">Named file in <tt>$GIT_DIR/remotes</tt></h3><div style="clear:left"></div>
926 in this file will be used to access the repository. The refspec
927 in this file will be used as default when you do not
928 provide a refspec on the command line. This file should have the
929 following format:</p></div>
932 <pre><tt> URL: one of the above URL format
935 </div></div>
939 be specified for additional branch mappings.</p></div>
940 <h3 id="_named_file_in_tt_git_dir_branches_tt">Named file in <tt>$GIT_DIR/branches</tt></h3><div style="clear:left"></div>
943 The URL in this file will be used to access the repository.
944 This file should have the following format:</p></div>
948 </div></div>
949 <div class="paragraph"><p><tt><url></tt> is required; <tt>#<head></tt> is optional.</p></div>
951 refspecs, if you don’t provide one on the command line.
958 </div></div>
963 </div></div>
964 </div>
968 <li>
969 <p>
970 Update the remote-tracking branches:
971 </p>
975 </div></div>
977 namespace and stores them to the local refs/remotes/origin/ namespace,
979 refspec.</p></div>
980 </li>
981 <li>
982 <p>
983 Using refspecs explicitly:
984 </p>
988 </div></div>
989 <div class="paragraph"><p>This updates (or creates, as necessary) branches <tt>pu</tt> and <tt>tmp</tt> in
990 the local repository by fetching from the branches (respectively)
992 <div class="paragraph"><p>The <tt>pu</tt> branch will be updated even if it is does not fast-forward,
994 </li>
995 </ul></div>
996 </div>
1000 </div>
1003 <div class="paragraph"><p>Written by Linus Torvalds <<a href="mailto:torvalds@osdl.org">torvalds@osdl.org</a>> and
1005 </div>
1008 <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>
1009 </div>
1013 </div>
1017 </div>
1018 </div>
1019 </body>
1020 </html>