| blob | e83a44103404ae52cc79b2862c274cd1298913a3 |
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 }
129 }
133 }
135 /* Block element titles. */
143 }
146 }
150 }
153 }
156 }
162 }
168 }
176 }
181 }
185 }
189 }
190 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
193 }
202 }
206 }
211 }
217 dl {
220 }
221 dt {
226 }
229 }
233 }
236 }
239 }
242 }
245 }
248 }
255 }
259 }
263 }
264 tfoot {
266 }
269 }
272 }
273 /* Because the table frame attribute is overriden by CSS in most browsers. */
276 }
280 }
284 }
290 }
293 }
296 }
302 }
305 }
309 }
313 }
317 }
321 }
326 }
330 }
340 }
345 }
347 div#toc {
349 }
351 div#toctitle {
358 }
363 }
367 }
371 }
375 }
376 /* Overrides for manpage documents */
377 h1 {
382 }
383 h2 {
385 }
388 }
392 }
394 /* Workarounds for IE6's broken and incomplete CSS2. */
400 }
407 }
413 }
418 }
422 }
426 }
431 }
433 /* IE6 sets dynamically generated links as visited. */
435 </style>
437 /*<![CDATA[*/
441 /////////////////////////////////////////////////////////////////////
442 // Table Of Contents generator
443 /////////////////////////////////////////////////////////////////////
445 /* Author: Mihai Bazon, September 2002
446 * http://students.infoiasi.ro/~mishoo
447 *
448 * Table Of Content generator
449 * Version: 0.4
450 *
451 * Feel free to use this script under the terms of the GNU General Public
452 * License, as long as you do not remove or alter this notice.
453 */
455 /* modified by Troy D. Hanson, September 2006. License: GPL */
456 /* modified by Stuart Rackham, 2006, 2009. License: GPL */
458 // toclevels = 1..4.
468 }
470 }
476 }
481 // Function that scans the DOM tree for header elements (the DOM2
482 // nodeIterator API would be a better technique but not supported by all
483 // browsers).
490 }
492 }
493 }
494 }
497 }
512 }
515 },
518 /////////////////////////////////////////////////////////////////////
519 // Footnotes generator
520 /////////////////////////////////////////////////////////////////////
522 /* Based on footnote generation code from:
523 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
524 */
534 n++;
535 // Use [\s\S] in place of . so multi-line matches work.
536 // Because JavaScript has no s (dotall) regex flag.
547 }
548 }
552 // Process footnoterefs.
561 }
562 }
563 }
564 }
566 }
567 /*]]>*/
568 </script>
569 </head>
570 <body>
572 <h1>
573 git-fetch(1) Manual Page
574 </h1>
577 <p>git-fetch -
578 Download objects and refs from another repository
579 </p>
580 </div>
581 </div>
586 <div class="verseblock-content"><em>git fetch</em> [<options>] [<repository> [<refspec>…]]
591 </div></div>
592 </div>
596 along with the objects necessary to complete them.</p></div>
600 <div class="paragraph"><p>When <refspec> stores the fetched result in remote-tracking branches,
601 the tags that point at these branches are automatically
602 followed. This is done by first fetching from the remote using
604 pointed by remote tags that it does not yet have, then fetch
605 those missing tags. If the other end has tags that point at
606 branches you are not interested in, you will not get them.</p></div>
611 </div>
616 --all
617 </dt>
618 <dd>
619 <p>
620 Fetch all remotes.
621 </p>
622 </dd>
624 -a
625 </dt>
627 --append
628 </dt>
629 <dd>
630 <p>
631 Append ref names and object names of fetched refs to the
634 </p>
635 </dd>
638 </dt>
639 <dd>
640 <p>
642 <tt>git clone</tt> with <tt>--depth=<depth></tt> option (see <a href="git-clone.html">git-clone(1)</a>)
643 by the specified number of commits.
644 </p>
645 </dd>
647 --dry-run
648 </dt>
649 <dd>
650 <p>
651 Show what would be done, without making any changes.
652 </p>
653 </dd>
655 -f
656 </dt>
658 --force
659 </dt>
660 <dd>
661 <p>
663 refspec, it refuses to update the local branch
666 overrides that check.
667 </p>
668 </dd>
670 -k
671 </dt>
673 --keep
674 </dt>
675 <dd>
676 <p>
677 Keep downloaded pack.
678 </p>
679 </dd>
681 --multiple
682 </dt>
683 <dd>
684 <p>
687 </p>
688 </dd>
690 -p
691 </dt>
693 --prune
694 </dt>
695 <dd>
696 <p>
697 After fetching, remove any remote-tracking branches which
698 no longer exist on the remote.
699 </p>
700 </dd>
702 -n
703 </dt>
705 --no-tags
706 </dt>
707 <dd>
708 <p>
709 By default, tags that point at objects that are downloaded
710 from the remote repository are fetched and stored locally.
711 This option disables this automatic tag following. The default
714 </p>
715 </dd>
717 -t
718 </dt>
720 --tags
721 </dt>
722 <dd>
723 <p>
724 Most of the tags are fetched automatically as branch
725 heads are downloaded, but tags that do not point at
726 objects reachable from the branch heads that are being
727 tracked will not be fetched by this mechanism. This
728 flag lets all tags and their associated objects be
729 downloaded. The default behavior for a remote may be
732 </p>
733 </dd>
735 --recurse-submodules[=yes|on-demand|no]
736 </dt>
737 <dd>
738 <p>
739 This option controls if and under what conditions new commits of
740 populated submodules should be fetched too. It can be used as a
742 unconditionally recurse into all populated submodules when set to
745 when the superproject retrieves a commit that updates the submodule’s
746 reference to a commit that isn’t already in the local submodule
747 clone.
748 </p>
749 </dd>
751 --no-recurse-submodules
752 </dt>
753 <dd>
754 <p>
755 Disable recursive fetching of submodules (this has the same effect as
757 </p>
758 </dd>
761 </dt>
762 <dd>
763 <p>
765 such as "Fetching submodule foo". This option is used
766 internally when recursing over submodules.
767 </p>
768 </dd>
770 --recurse-submodules-default=[yes|on-demand]
771 </dt>
772 <dd>
773 <p>
774 This option is used internally to temporarily provide a
775 non-negative default value for the --recurse-submodules
776 option. All other methods of configuring fetch’s submodule
779 specifying --[no-]recurse-submodules directly.
780 </p>
781 </dd>
783 -u
784 </dt>
786 --update-head-ok
787 </dt>
788 <dd>
789 <p>
791 corresponds to the current branch. This flag disables the
794 implementing your own Porcelain you are not supposed to
795 use it.
796 </p>
797 </dd>
800 </dt>
801 <dd>
802 <p>
803 When given, and the repository to fetch from is handled
805 the command to specify non-default path for the command
806 run on the other end.
807 </p>
808 </dd>
810 -q
811 </dt>
813 --quiet
814 </dt>
815 <dd>
816 <p>
817 Pass --quiet to git-fetch-pack and silence any other internally
818 used git commands. Progress is not reported to the standard error
819 stream.
820 </p>
821 </dd>
823 -v
824 </dt>
826 --verbose
827 </dt>
828 <dd>
829 <p>
830 Be verbose.
831 </p>
832 </dd>
834 --progress
835 </dt>
836 <dd>
837 <p>
838 Progress status is reported on the standard error stream
839 by default when it is attached to a terminal, unless -q
840 is specified. This flag forces progress status even if the
841 standard error stream is not directed to a terminal.
842 </p>
843 </dd>
846 </dt>
847 <dd>
848 <p>
849 The "remote" repository that is the source of a fetch
850 or pull operation. This parameter can be either a URL
853 </p>
854 </dd>
857 </dt>
858 <dd>
859 <p>
860 A name referring to a list of repositories as the value
863 </p>
864 </dd>
867 </dt>
868 <dd>
869 <p>
873 </p>
878 is updated even if it does not result in a fast-forward
879 update.</p></div>
881 <table><tr>
884 </td>
886 modified in non-linear ways such as being rewound and
887 rebased frequently, then a pull will attempt a merge with
888 an older version of itself, likely conflict, and fail.
889 It is under these conditions that you would want to use
891 be needed. There is currently no easy way to determine
892 or declare that a branch will be made available in a
893 repository with this behavior; the pulling user simply
894 must know this is the expected usage pattern for a branch.</td>
895 </tr></table>
896 </div>
898 <table><tr>
901 </td>
910 the progress of the remote side, and when you see something new
911 on the remote branch, merge it into your development branch with
913 </tr></table>
914 </div>
916 <table><tr>
919 </td>
925 merged into the current branch after fetching. In other words,
926 if you list more than one remote refs, you would be making
930 after fetching all the remote refs. This is because making an
931 Octopus from remote refs is rarely done, while keeping track
932 of multiple remote heads in one-go by fetching more than one
933 is often useful.</td>
934 </tr></table>
935 </div>
938 <li>
939 <p>
940 <tt>tag <tag></tt> means the same as <tt>refs/tags/<tag>:refs/tags/<tag></tt>;
941 it requests fetching everything up to the given tag.
942 </p>
943 </li>
944 <li>
945 <p>
948 branch without storing the remote branch anywhere locally
949 </p>
950 </li>
951 </ul></div>
952 </dd>
953 </dl></div>
954 </div>
957 <div class="paragraph"><p>In general, URLs contain information about the transport protocol, the
958 address of the remote server, and the path to the repository.
959 Depending on the transport protocol, some of this information may be
960 absent.</p></div>
962 protocols. The following syntaxes may be used with them:</p></div>
964 <li>
965 <p>
967 </p>
968 </li>
969 <li>
970 <p>
972 </p>
973 </li>
974 <li>
975 <p>
977 </p>
978 </li>
979 <li>
980 <p>
982 </p>
983 </li>
984 <li>
985 <p>
986 rsync://host.xz/path/to/repo.git/
987 </p>
988 </li>
989 </ul></div>
990 <div class="paragraph"><p>An alternative scp-like syntax may also be used with the ssh protocol:</p></div>
992 <li>
993 <p>
995 </p>
996 </li>
997 </ul></div>
998 <div class="paragraph"><p>The ssh and git protocols additionally support ~username expansion:</p></div>
1000 <li>
1001 <p>
1003 </p>
1004 </li>
1005 <li>
1006 <p>
1008 </p>
1009 </li>
1010 <li>
1011 <p>
1013 </p>
1014 </li>
1015 </ul></div>
1016 <div class="paragraph"><p>For local repositories, also supported by git natively, the following
1017 syntaxes may be used:</p></div>
1019 <li>
1020 <p>
1021 /path/to/repo.git/
1022 </p>
1023 </li>
1024 <li>
1025 <p>
1027 </p>
1028 </li>
1029 </ul></div>
1032 details.</p></div>
1033 <div class="paragraph"><p>When git doesn’t know how to handle a certain transport protocol, it
1035 exists. To explicitly request a remote helper, the following syntax
1036 may be used:</p></div>
1038 <li>
1039 <p>
1041 </p>
1042 </li>
1043 </ul></div>
1044 <div class="paragraph"><p>where <address> may be a path, a server and path, or an arbitrary
1045 URL-like string recognized by the specific remote helper being
1046 invoked. See <a href="git-remote-helpers.html">git-remote-helpers(1)</a> for details.</p></div>
1047 <div class="paragraph"><p>If there are a large number of similarly-named remote repositories and
1048 you want to use a different format for them (such that the URLs you
1049 use will be rewritten into URLs that work), you can create a
1050 configuration section of the form:</p></div>
1055 </div></div>
1060 insteadOf = host.xz:/path/to/
1061 insteadOf = work:</tt></pre>
1062 </div></div>
1063 <div class="paragraph"><p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
1066 configuration section of the form:</p></div>
1071 </div></div>
1076 pushInsteadOf = git://example.org/</tt></pre>
1077 </div></div>
1079 "ssh://example.org/path/to/repo.git" for pushes, but pulls will still
1080 use the original URL.</p></div>
1081 </div>
1087 <li>
1088 <p>
1090 </p>
1091 </li>
1092 <li>
1093 <p>
1095 </p>
1096 </li>
1097 <li>
1098 <p>
1100 </p>
1101 </li>
1102 </ul></div>
1103 <div class="paragraph"><p>All of these also allow you to omit the refspec from the command line
1104 because they each contain a refspec which git will use by default.</p></div>
1105 <h3 id="_named_remote_in_configuration_file">Named remote in configuration file</h3><div style="clear:left"></div>
1106 <div class="paragraph"><p>You can choose to provide the name of a remote which you had previously
1107 configured using <a href="git-remote.html">git-remote(1)</a>, <a href="git-config.html">git-config(1)</a>
1109 this remote will be used to access the repository. The refspec
1110 of this remote will be used by default when you do
1111 not provide a refspec on the command line. The entry in the
1112 config file would appear like this:</p></div>
1120 </div></div>
1121 <div class="paragraph"><p>The <tt><pushurl></tt> is used for pushes only. It is optional and defaults
1123 <h3 id="_named_file_in_tt_git_dir_remotes_tt">Named file in <tt>$GIT_DIR/remotes</tt></h3><div style="clear:left"></div>
1126 in this file will be used to access the repository. The refspec
1127 in this file will be used as default when you do not
1128 provide a refspec on the command line. This file should have the
1129 following format:</p></div>
1132 <pre><tt> URL: one of the above URL format
1135 </div></div>
1139 be specified for additional branch mappings.</p></div>
1140 <h3 id="_named_file_in_tt_git_dir_branches_tt">Named file in <tt>$GIT_DIR/branches</tt></h3><div style="clear:left"></div>
1143 The URL in this file will be used to access the repository.
1144 This file should have the following format:</p></div>
1148 </div></div>
1149 <div class="paragraph"><p><tt><url></tt> is required; <tt>#<head></tt> is optional.</p></div>
1151 refspecs, if you don’t provide one on the command line.
1158 </div></div>
1163 </div></div>
1164 </div>
1168 <li>
1169 <p>
1170 Update the remote-tracking branches:
1171 </p>
1175 </div></div>
1177 namespace and stores them to the local refs/remotes/origin/ namespace,
1179 refspec.</p></div>
1180 </li>
1181 <li>
1182 <p>
1183 Using refspecs explicitly:
1184 </p>
1188 </div></div>
1189 <div class="paragraph"><p>This updates (or creates, as necessary) branches <tt>pu</tt> and <tt>tmp</tt> in
1190 the local repository by fetching from the branches (respectively)
1192 <div class="paragraph"><p>The <tt>pu</tt> branch will be updated even if it is does not fast-forward,
1194 </li>
1195 </ul></div>
1196 </div>
1199 <div class="paragraph"><p>Using --recurse-submodules can only fetch new commits in already checked
1200 out submodules right now. When e.g. upstream added a new submodule in the
1201 just fetched commits of the superproject the submodule itself can not be
1202 fetched, making it impossible to check out that submodule later without
1203 having to do a fetch again. This is expected to be fixed in a future git
1204 version.</p></div>
1205 </div>
1209 </div>
1213 </div>
1214 </div>
1219 </div>
1220 </div>
1221 </body>
1222 </html>