| blob | f88b40ed6a28823728c844a61ef2927ece7d1208 |
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>
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 --recurse-submodules[=yes|on-demand|no]
565 </dt>
566 <dd>
567 <p>
568 This option controls if and under what conditions new commits of
569 populated submodules should be fetched too. It can be used as a
571 unconditionally recurse into all populated submodules when set to
574 when the superproject retrieves a commit that updates the submodule’s
575 reference to a commit that isn’t already in the local submodule
576 clone.
577 </p>
578 </dd>
580 --no-recurse-submodules
581 </dt>
582 <dd>
583 <p>
584 Disable recursive fetching of submodules (this has the same effect as
586 </p>
587 </dd>
590 </dt>
591 <dd>
592 <p>
594 such as "Fetching submodule foo". This option is used
595 internally when recursing over submodules.
596 </p>
597 </dd>
599 --recurse-submodules-default=[yes|on-demand]
600 </dt>
601 <dd>
602 <p>
603 This option is used internally to temporarily provide a
604 non-negative default value for the --recurse-submodules
605 option. All other methods of configuring fetch’s submodule
608 specifying --[no-]recurse-submodules directly.
609 </p>
610 </dd>
612 -u
613 </dt>
615 --update-head-ok
616 </dt>
617 <dd>
618 <p>
620 corresponds to the current branch. This flag disables the
623 implementing your own Porcelain you are not supposed to
624 use it.
625 </p>
626 </dd>
629 </dt>
630 <dd>
631 <p>
632 When given, and the repository to fetch from is handled
634 the command to specify non-default path for the command
635 run on the other end.
636 </p>
637 </dd>
639 -q
640 </dt>
642 --quiet
643 </dt>
644 <dd>
645 <p>
646 Pass --quiet to git-fetch-pack and silence any other internally
647 used git commands. Progress is not reported to the standard error
648 stream.
649 </p>
650 </dd>
652 -v
653 </dt>
655 --verbose
656 </dt>
657 <dd>
658 <p>
659 Be verbose.
660 </p>
661 </dd>
663 --progress
664 </dt>
665 <dd>
666 <p>
667 Progress status is reported on the standard error stream
668 by default when it is attached to a terminal, unless -q
669 is specified. This flag forces progress status even if the
670 standard error stream is not directed to a terminal.
671 </p>
672 </dd>
675 </dt>
676 <dd>
677 <p>
678 The "remote" repository that is the source of a fetch
679 or pull operation. This parameter can be either a URL
682 </p>
683 </dd>
686 </dt>
687 <dd>
688 <p>
689 A name referring to a list of repositories as the value
692 </p>
693 </dd>
696 </dt>
697 <dd>
698 <p>
702 </p>
707 is updated even if it does not result in a fast-forward
708 update.</p></div>
710 <table><tr>
713 </td>
715 modified in non-linear ways such as being rewound and
716 rebased frequently, then a pull will attempt a merge with
717 an older version of itself, likely conflict, and fail.
718 It is under these conditions that you would want to use
720 be needed. There is currently no easy way to determine
721 or declare that a branch will be made available in a
722 repository with this behavior; the pulling user simply
723 must know this is the expected usage pattern for a branch.</td>
724 </tr></table>
725 </div>
727 <table><tr>
730 </td>
739 the progress of the remote side, and when you see something new
740 on the remote branch, merge it into your development branch with
742 </tr></table>
743 </div>
745 <table><tr>
748 </td>
754 merged into the current branch after fetching. In other words,
755 if you list more than one remote refs, you would be making
759 after fetching all the remote refs. This is because making an
760 Octopus from remote refs is rarely done, while keeping track
761 of multiple remote heads in one-go by fetching more than one
762 is often useful.</td>
763 </tr></table>
764 </div>
767 <li>
768 <p>
769 <tt>tag <tag></tt> means the same as <tt>refs/tags/<tag>:refs/tags/<tag></tt>;
770 it requests fetching everything up to the given tag.
771 </p>
772 </li>
773 <li>
774 <p>
777 branch without storing the remote branch anywhere locally
778 </p>
779 </li>
780 </ul></div>
781 </dd>
782 </dl></div>
783 </div>
786 <div class="paragraph"><p>In general, URLs contain information about the transport protocol, the
787 address of the remote server, and the path to the repository.
788 Depending on the transport protocol, some of this information may be
789 absent.</p></div>
791 protocols. The following syntaxes may be used with them:</p></div>
793 <li>
794 <p>
796 </p>
797 </li>
798 <li>
799 <p>
801 </p>
802 </li>
803 <li>
804 <p>
806 </p>
807 </li>
808 <li>
809 <p>
811 </p>
812 </li>
813 <li>
814 <p>
815 rsync://host.xz/path/to/repo.git/
816 </p>
817 </li>
818 </ul></div>
819 <div class="paragraph"><p>An alternative scp-like syntax may also be used with the ssh protocol:</p></div>
821 <li>
822 <p>
824 </p>
825 </li>
826 </ul></div>
827 <div class="paragraph"><p>The ssh and git protocols additionally support ~username expansion:</p></div>
829 <li>
830 <p>
832 </p>
833 </li>
834 <li>
835 <p>
837 </p>
838 </li>
839 <li>
840 <p>
842 </p>
843 </li>
844 </ul></div>
846 syntaxes may be used:</p></div>
848 <li>
849 <p>
850 /path/to/repo.git/
851 </p>
852 </li>
853 <li>
854 <p>
856 </p>
857 </li>
858 </ul></div>
861 details.</p></div>
862 <div class="paragraph"><p>When git doesn’t know how to handle a certain transport protocol, it
864 exists. To explicitly request a remote helper, the following syntax
865 may be used:</p></div>
867 <li>
868 <p>
870 </p>
871 </li>
872 </ul></div>
873 <div class="paragraph"><p>where <address> may be a path, a server and path, or an arbitrary
874 URL-like string recognized by the specific remote helper being
876 <div class="paragraph"><p>If there are a large number of similarly-named remote repositories and
877 you want to use a different format for them (such that the URLs you
878 use will be rewritten into URLs that work), you can create a
879 configuration section of the form:</p></div>
884 </div></div>
889 insteadOf = host.xz:/path/to/
890 insteadOf = work:</tt></pre>
891 </div></div>
892 <div class="paragraph"><p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
895 configuration section of the form:</p></div>
900 </div></div>
905 pushInsteadOf = git://example.org/</tt></pre>
906 </div></div>
908 "ssh://example.org/path/to/repo.git" for pushes, but pulls will still
909 use the original URL.</p></div>
910 </div>
916 <li>
917 <p>
919 </p>
920 </li>
921 <li>
922 <p>
924 </p>
925 </li>
926 <li>
927 <p>
929 </p>
930 </li>
931 </ul></div>
933 because they each contain a refspec which git will use by default.</p></div>
934 <h3 id="_named_remote_in_configuration_file">Named remote in configuration file</h3><div style="clear:left"></div>
935 <div class="paragraph"><p>You can choose to provide the name of a remote which you had previously
936 configured using <a href="git-remote.html">git-remote(1)</a>, <a href="git-config.html">git-config(1)</a>
938 this remote will be used to access the repository. The refspec
939 of this remote will be used by default when you do
940 not provide a refspec on the command line. The entry in the
941 config file would appear like this:</p></div>
949 </div></div>
950 <div class="paragraph"><p>The <tt><pushurl></tt> is used for pushes only. It is optional and defaults
952 <h3 id="_named_file_in_tt_git_dir_remotes_tt">Named file in <tt>$GIT_DIR/remotes</tt></h3><div style="clear:left"></div>
955 in this file will be used to access the repository. The refspec
956 in this file will be used as default when you do not
957 provide a refspec on the command line. This file should have the
958 following format:</p></div>
961 <pre><tt> URL: one of the above URL format
964 </div></div>
968 be specified for additional branch mappings.</p></div>
969 <h3 id="_named_file_in_tt_git_dir_branches_tt">Named file in <tt>$GIT_DIR/branches</tt></h3><div style="clear:left"></div>
972 The URL in this file will be used to access the repository.
973 This file should have the following format:</p></div>
977 </div></div>
978 <div class="paragraph"><p><tt><url></tt> is required; <tt>#<head></tt> is optional.</p></div>
980 refspecs, if you don’t provide one on the command line.
987 </div></div>
992 </div></div>
993 </div>
997 <li>
998 <p>
999 Update the remote-tracking branches:
1000 </p>
1004 </div></div>
1006 namespace and stores them to the local refs/remotes/origin/ namespace,
1008 refspec.</p></div>
1009 </li>
1010 <li>
1011 <p>
1012 Using refspecs explicitly:
1013 </p>
1017 </div></div>
1018 <div class="paragraph"><p>This updates (or creates, as necessary) branches <tt>pu</tt> and <tt>tmp</tt> in
1019 the local repository by fetching from the branches (respectively)
1021 <div class="paragraph"><p>The <tt>pu</tt> branch will be updated even if it is does not fast-forward,
1023 </li>
1024 </ul></div>
1025 </div>
1028 <div class="paragraph"><p>Using --recurse-submodules can only fetch new commits in already checked
1029 out submodules right now. When e.g. upstream added a new submodule in the
1030 just fetched commits of the superproject the submodule itself can not be
1031 fetched, making it impossible to check out that submodule later without
1032 having to do a fetch again. This is expected to be fixed in a future git
1033 version.</p></div>
1034 </div>
1038 </div>
1042 </div>
1046 </div>
1047 </div>
1048 </body>
1049 </html>