| blob | 082029202146e47a9d989c2c9cce1059efbda04c |
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>
418 <div class="verseblock-content"><em>git fetch</em> [<options>] [<repository> [<refspec>…]]
423 </div></div>
424 </div>
428 along with the objects necessary to complete them.</p></div>
432 <div class="paragraph"><p>When <refspec> stores the fetched result in remote-tracking branches,
433 the tags that point at these branches are automatically
434 followed. This is done by first fetching from the remote using
436 pointed by remote tags that it does not yet have, then fetch
437 those missing tags. If the other end has tags that point at
438 branches you are not interested in, you will not get them.</p></div>
443 </div>
448 --all
449 </dt>
450 <dd>
451 <p>
452 Fetch all remotes.
453 </p>
454 </dd>
456 -a
457 </dt>
459 --append
460 </dt>
461 <dd>
462 <p>
463 Append ref names and object names of fetched refs to the
466 </p>
467 </dd>
470 </dt>
471 <dd>
472 <p>
474 <tt>git clone</tt> with <tt>--depth=<depth></tt> option (see <a href="git-clone.html">git-clone(1)</a>)
475 by the specified number of commits.
476 </p>
477 </dd>
479 --dry-run
480 </dt>
481 <dd>
482 <p>
483 Show what would be done, without making any changes.
484 </p>
485 </dd>
487 -f
488 </dt>
490 --force
491 </dt>
492 <dd>
493 <p>
495 refspec, it refuses to update the local branch
498 overrides that check.
499 </p>
500 </dd>
502 -k
503 </dt>
505 --keep
506 </dt>
507 <dd>
508 <p>
509 Keep downloaded pack.
510 </p>
511 </dd>
513 --multiple
514 </dt>
515 <dd>
516 <p>
519 </p>
520 </dd>
522 -p
523 </dt>
525 --prune
526 </dt>
527 <dd>
528 <p>
529 After fetching, remove any remote-tracking branches which
530 no longer exist on the remote.
531 </p>
532 </dd>
534 -n
535 </dt>
537 --no-tags
538 </dt>
539 <dd>
540 <p>
541 By default, tags that point at objects that are downloaded
542 from the remote repository are fetched and stored locally.
543 This option disables this automatic tag following. The default
546 </p>
547 </dd>
549 -t
550 </dt>
552 --tags
553 </dt>
554 <dd>
555 <p>
556 Most of the tags are fetched automatically as branch
557 heads are downloaded, but tags that do not point at
558 objects reachable from the branch heads that are being
559 tracked will not be fetched by this mechanism. This
560 flag lets all tags and their associated objects be
561 downloaded. The default behavior for a remote may be
564 </p>
565 </dd>
567 --recurse-submodules[=yes|on-demand|no]
568 </dt>
569 <dd>
570 <p>
571 This option controls if and under what conditions new commits of
572 populated submodules should be fetched too. It can be used as a
574 unconditionally recurse into all populated submodules when set to
577 when the superproject retrieves a commit that updates the submodule’s
578 reference to a commit that isn’t already in the local submodule
579 clone.
580 </p>
581 </dd>
583 --no-recurse-submodules
584 </dt>
585 <dd>
586 <p>
587 Disable recursive fetching of submodules (this has the same effect as
589 </p>
590 </dd>
593 </dt>
594 <dd>
595 <p>
597 such as "Fetching submodule foo". This option is used
598 internally when recursing over submodules.
599 </p>
600 </dd>
602 --recurse-submodules-default=[yes|on-demand]
603 </dt>
604 <dd>
605 <p>
606 This option is used internally to temporarily provide a
607 non-negative default value for the --recurse-submodules
608 option. All other methods of configuring fetch’s submodule
611 specifying --[no-]recurse-submodules directly.
612 </p>
613 </dd>
615 -u
616 </dt>
618 --update-head-ok
619 </dt>
620 <dd>
621 <p>
623 corresponds to the current branch. This flag disables the
626 implementing your own Porcelain you are not supposed to
627 use it.
628 </p>
629 </dd>
632 </dt>
633 <dd>
634 <p>
635 When given, and the repository to fetch from is handled
637 the command to specify non-default path for the command
638 run on the other end.
639 </p>
640 </dd>
642 -q
643 </dt>
645 --quiet
646 </dt>
647 <dd>
648 <p>
649 Pass --quiet to git-fetch-pack and silence any other internally
650 used git commands. Progress is not reported to the standard error
651 stream.
652 </p>
653 </dd>
655 -v
656 </dt>
658 --verbose
659 </dt>
660 <dd>
661 <p>
662 Be verbose.
663 </p>
664 </dd>
666 --progress
667 </dt>
668 <dd>
669 <p>
670 Progress status is reported on the standard error stream
671 by default when it is attached to a terminal, unless -q
672 is specified. This flag forces progress status even if the
673 standard error stream is not directed to a terminal.
674 </p>
675 </dd>
678 </dt>
679 <dd>
680 <p>
681 The "remote" repository that is the source of a fetch
682 or pull operation. This parameter can be either a URL
685 </p>
686 </dd>
689 </dt>
690 <dd>
691 <p>
692 A name referring to a list of repositories as the value
695 </p>
696 </dd>
699 </dt>
700 <dd>
701 <p>
705 </p>
710 is updated even if it does not result in a fast-forward
711 update.</p></div>
713 <table><tr>
716 </td>
718 modified in non-linear ways such as being rewound and
719 rebased frequently, then a pull will attempt a merge with
720 an older version of itself, likely conflict, and fail.
721 It is under these conditions that you would want to use
723 be needed. There is currently no easy way to determine
724 or declare that a branch will be made available in a
725 repository with this behavior; the pulling user simply
726 must know this is the expected usage pattern for a branch.</td>
727 </tr></table>
728 </div>
730 <table><tr>
733 </td>
742 the progress of the remote side, and when you see something new
743 on the remote branch, merge it into your development branch with
745 </tr></table>
746 </div>
748 <table><tr>
751 </td>
757 merged into the current branch after fetching. In other words,
758 if you list more than one remote refs, you would be making
762 after fetching all the remote refs. This is because making an
763 Octopus from remote refs is rarely done, while keeping track
764 of multiple remote heads in one-go by fetching more than one
765 is often useful.</td>
766 </tr></table>
767 </div>
770 <li>
771 <p>
772 <tt>tag <tag></tt> means the same as <tt>refs/tags/<tag>:refs/tags/<tag></tt>;
773 it requests fetching everything up to the given tag.
774 </p>
775 </li>
776 <li>
777 <p>
780 branch without storing the remote branch anywhere locally
781 </p>
782 </li>
783 </ul></div>
784 </dd>
785 </dl></div>
786 </div>
789 <div class="paragraph"><p>In general, URLs contain information about the transport protocol, the
790 address of the remote server, and the path to the repository.
791 Depending on the transport protocol, some of this information may be
792 absent.</p></div>
794 protocols. The following syntaxes may be used with them:</p></div>
796 <li>
797 <p>
799 </p>
800 </li>
801 <li>
802 <p>
804 </p>
805 </li>
806 <li>
807 <p>
809 </p>
810 </li>
811 <li>
812 <p>
814 </p>
815 </li>
816 <li>
817 <p>
818 rsync://host.xz/path/to/repo.git/
819 </p>
820 </li>
821 </ul></div>
822 <div class="paragraph"><p>An alternative scp-like syntax may also be used with the ssh protocol:</p></div>
824 <li>
825 <p>
827 </p>
828 </li>
829 </ul></div>
830 <div class="paragraph"><p>The ssh and git protocols additionally support ~username expansion:</p></div>
832 <li>
833 <p>
835 </p>
836 </li>
837 <li>
838 <p>
840 </p>
841 </li>
842 <li>
843 <p>
845 </p>
846 </li>
847 </ul></div>
849 syntaxes may be used:</p></div>
851 <li>
852 <p>
853 /path/to/repo.git/
854 </p>
855 </li>
856 <li>
857 <p>
859 </p>
860 </li>
861 </ul></div>
864 details.</p></div>
865 <div class="paragraph"><p>When git doesn’t know how to handle a certain transport protocol, it
867 exists. To explicitly request a remote helper, the following syntax
868 may be used:</p></div>
870 <li>
871 <p>
873 </p>
874 </li>
875 </ul></div>
876 <div class="paragraph"><p>where <address> may be a path, a server and path, or an arbitrary
877 URL-like string recognized by the specific remote helper being
879 <div class="paragraph"><p>If there are a large number of similarly-named remote repositories and
880 you want to use a different format for them (such that the URLs you
881 use will be rewritten into URLs that work), you can create a
882 configuration section of the form:</p></div>
887 </div></div>
892 insteadOf = host.xz:/path/to/
893 insteadOf = work:</tt></pre>
894 </div></div>
895 <div class="paragraph"><p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
898 configuration section of the form:</p></div>
903 </div></div>
908 pushInsteadOf = git://example.org/</tt></pre>
909 </div></div>
911 "ssh://example.org/path/to/repo.git" for pushes, but pulls will still
912 use the original URL.</p></div>
913 </div>
919 <li>
920 <p>
922 </p>
923 </li>
924 <li>
925 <p>
927 </p>
928 </li>
929 <li>
930 <p>
932 </p>
933 </li>
934 </ul></div>
936 because they each contain a refspec which git will use by default.</p></div>
937 <h3 id="_named_remote_in_configuration_file">Named remote in configuration file</h3><div style="clear:left"></div>
938 <div class="paragraph"><p>You can choose to provide the name of a remote which you had previously
939 configured using <a href="git-remote.html">git-remote(1)</a>, <a href="git-config.html">git-config(1)</a>
941 this remote will be used to access the repository. The refspec
942 of this remote will be used by default when you do
943 not provide a refspec on the command line. The entry in the
944 config file would appear like this:</p></div>
952 </div></div>
953 <div class="paragraph"><p>The <tt><pushurl></tt> is used for pushes only. It is optional and defaults
955 <h3 id="_named_file_in_tt_git_dir_remotes_tt">Named file in <tt>$GIT_DIR/remotes</tt></h3><div style="clear:left"></div>
958 in this file will be used to access the repository. The refspec
959 in this file will be used as default when you do not
960 provide a refspec on the command line. This file should have the
961 following format:</p></div>
964 <pre><tt> URL: one of the above URL format
967 </div></div>
971 be specified for additional branch mappings.</p></div>
972 <h3 id="_named_file_in_tt_git_dir_branches_tt">Named file in <tt>$GIT_DIR/branches</tt></h3><div style="clear:left"></div>
975 The URL in this file will be used to access the repository.
976 This file should have the following format:</p></div>
980 </div></div>
981 <div class="paragraph"><p><tt><url></tt> is required; <tt>#<head></tt> is optional.</p></div>
983 refspecs, if you don’t provide one on the command line.
990 </div></div>
995 </div></div>
996 </div>
1000 <li>
1001 <p>
1002 Update the remote-tracking branches:
1003 </p>
1007 </div></div>
1009 namespace and stores them to the local refs/remotes/origin/ namespace,
1011 refspec.</p></div>
1012 </li>
1013 <li>
1014 <p>
1015 Using refspecs explicitly:
1016 </p>
1020 </div></div>
1021 <div class="paragraph"><p>This updates (or creates, as necessary) branches <tt>pu</tt> and <tt>tmp</tt> in
1022 the local repository by fetching from the branches (respectively)
1024 <div class="paragraph"><p>The <tt>pu</tt> branch will be updated even if it is does not fast-forward,
1026 </li>
1027 </ul></div>
1028 </div>
1031 <div class="paragraph"><p>Using --recurse-submodules can only fetch new commits in already checked
1032 out submodules right now. When e.g. upstream added a new submodule in the
1033 just fetched commits of the superproject the submodule itself can not be
1034 fetched, making it impossible to check out that submodule later without
1035 having to do a fetch again. This is expected to be fixed in a future git
1036 version.</p></div>
1037 </div>
1041 </div>
1045 </div>
1049 </div>
1050 </div>
1051 </body>
1052 </html>