| blob | fd16260db98344127a05a3ca3fb531b0208dd1f8 |
4 <head>
8 /* Debug borders */
10 /*
11 border: 1px solid red;
12 */
13 }
15 body {
17 }
19 a {
22 }
25 }
27 em {
29 }
31 strong {
33 }
35 tt {
37 }
45 }
49 }
50 h2 {
52 }
53 h3 {
55 }
56 h3 + * {
58 }
63 }
65 hr {
67 }
69 p {
72 }
74 pre {
77 }
79 span#author {
84 }
85 span#email {
86 }
87 span#revision {
89 }
91 div#footer {
97 }
98 div#footer-text {
101 }
102 div#footer-badges {
105 }
107 div#preamble,
114 }
118 }
122 }
124 /* Block element titles. */
131 }
134 }
138 }
141 }
144 }
150 }
154 }
159 }
163 }
167 }
170 }
179 }
183 }
188 }
192 }
198 dl {
201 }
202 dt {
206 }
209 }
213 }
216 }
220 }
221 thead {
224 }
225 tfoot {
227 }
232 }
235 }
240 }
243 }
247 }
249 div#toctitle {
256 }
261 }
265 }
269 }
273 }
275 /* Workarounds for IE6's broken and incomplete CSS2. */
281 }
287 }
293 }
297 }
302 }
304 /* IE6 sets dynamically generated links as visited. */
306 </style>
308 </head>
309 <body>
311 <h1>
312 git-fetch(1) Manual Page
313 </h1>
316 <p>git-fetch -
317 Download objects and refs from another repository
318 </p>
319 </div>
320 </div>
323 <div class="para"><p><em>git fetch</em> [<options>] [<repository> [<refspec>…]]</p></div>
325 <div class="para"><p><em>git fetch</em> --multiple [<options>] [<repository> | <group>]…</p></div>
327 </div>
331 along with the objects necessary to complete them.</p></div>
336 the tags that point at these branches are automatically
337 followed. This is done by first fetching from the remote using
339 pointed by remote tags that it does not yet have, then fetch
340 those missing tags. If the other end has tags that point at
341 branches you are not interested in, you will not get them.</p></div>
346 </div>
350 <dt>
351 --all
352 </dt>
353 <dd>
354 <p>
355 Fetch all remotes.
356 </p>
357 </dd>
358 <dt>
359 -a
360 </dt>
361 <dt>
362 --append
363 </dt>
364 <dd>
365 <p>
366 Append ref names and object names of fetched refs to the
369 </p>
370 </dd>
371 <dt>
373 </dt>
374 <dd>
375 <p>
377 <tt>git clone</tt> with <tt>--depth=<depth></tt> option (see <a href="git-clone.html">git-clone(1)</a>)
378 by the specified number of commits.
379 </p>
380 </dd>
381 <dt>
382 --dry-run
383 </dt>
384 <dd>
385 <p>
386 Show what would be done, without making any changes.
387 </p>
388 </dd>
389 <dt>
390 -f
391 </dt>
392 <dt>
393 --force
394 </dt>
395 <dd>
396 <p>
398 refspec, it refuses to update the local branch
401 overrides that check.
402 </p>
403 </dd>
404 <dt>
405 -k
406 </dt>
407 <dt>
408 --keep
409 </dt>
410 <dd>
411 <p>
412 Keep downloaded pack.
413 </p>
414 </dd>
415 <dt>
416 --multiple
417 </dt>
418 <dd>
419 <p>
422 </p>
423 </dd>
424 <dt>
425 --prune
426 </dt>
427 <dd>
428 <p>
429 After fetching, remove any remote tracking branches which
430 no longer exist on the remote.
431 </p>
432 </dd>
433 <dt>
434 -n
435 </dt>
436 <dt>
437 --no-tags
438 </dt>
439 <dd>
440 <p>
441 By default, tags that point at objects that are downloaded
442 from the remote repository are fetched and stored locally.
443 This option disables this automatic tag following.
444 </p>
445 </dd>
446 <dt>
447 -t
448 </dt>
449 <dt>
450 --tags
451 </dt>
452 <dd>
453 <p>
454 Most of the tags are fetched automatically as branch
455 heads are downloaded, but tags that do not point at
456 objects reachable from the branch heads that are being
457 tracked will not be fetched by this mechanism. This
458 flag lets all tags and their associated objects be
459 downloaded.
460 </p>
461 </dd>
462 <dt>
463 -u
464 </dt>
465 <dt>
466 --update-head-ok
467 </dt>
468 <dd>
469 <p>
471 corresponds to the current branch. This flag disables the
474 implementing your own Porcelain you are not supposed to
475 use it.
476 </p>
477 </dd>
478 <dt>
480 </dt>
481 <dd>
482 <p>
483 When given, and the repository to fetch from is handled
485 the command to specify non-default path for the command
486 run on the other end.
487 </p>
488 </dd>
489 <dt>
490 -q
491 </dt>
492 <dt>
493 --quiet
494 </dt>
495 <dd>
496 <p>
497 Pass --quiet to git-fetch-pack and silence any other internally
498 used git commands. Progress is not reported to the standard error
499 stream.
500 </p>
501 </dd>
502 <dt>
503 -v
504 </dt>
505 <dt>
506 --verbose
507 </dt>
508 <dd>
509 <p>
510 Be verbose.
511 </p>
512 </dd>
513 <dt>
514 --progress
515 </dt>
516 <dd>
517 <p>
518 Progress status is reported on the standard error stream
519 by default when it is attached to a terminal, unless -q
520 is specified. This flag forces progress status even if the
521 standard error stream is not directed to a terminal.
522 </p>
523 </dd>
524 <dt>
526 </dt>
527 <dd>
528 <p>
529 The "remote" repository that is the source of a fetch
530 or pull operation. This parameter can be either a URL
533 </p>
534 </dd>
535 <dt>
537 </dt>
538 <dd>
539 <p>
540 A name referring to a list of repositories as the value
543 </p>
544 </dd>
545 <dt>
547 </dt>
548 <dd>
549 <p>
553 </p>
558 is updated even if it does not result in a fast-forward
559 update.</p></div>
561 <table><tr>
564 </td>
566 modified in non-linear ways such as being rewound and
567 rebased frequently, then a pull will attempt a merge with
568 an older version of itself, likely conflict, and fail.
569 It is under these conditions that you would want to use
571 be needed. There is currently no easy way to determine
572 or declare that a branch will be made available in a
573 repository with this behavior; the pulling user simply
574 must know this is the expected usage pattern for a branch.</td>
575 </tr></table>
576 </div>
578 <table><tr>
581 </td>
590 the progress of the remote side, and when you see something new
591 on the remote branch, merge it into your development branch with
593 </tr></table>
594 </div>
596 <table><tr>
599 </td>
605 merged into the current branch after fetching. In other words,
606 if you list more than one remote refs, you would be making
610 after fetching all the remote refs. This is because making an
611 Octopus from remote refs is rarely done, while keeping track
612 of multiple remote heads in one-go by fetching more than one
613 is often useful.</td>
614 </tr></table>
615 </div>
618 <li>
619 <p>
620 <tt>tag <tag></tt> means the same as <tt>refs/tags/<tag>:refs/tags/<tag></tt>;
621 it requests fetching everything up to the given tag.
622 </p>
623 </li>
624 <li>
625 <p>
628 branch without storing the remote branch anywhere locally
629 </p>
630 </li>
631 </ul></div>
632 </dd>
633 </dl></div>
634 </div>
638 address of the remote server, and the path to the repository.
639 Depending on the transport protocol, some of this information may be
640 absent.</p></div>
642 protocols. The following syntaxes may be used with them:</p></div>
644 <li>
645 <p>
647 </p>
648 </li>
649 <li>
650 <p>
652 </p>
653 </li>
654 <li>
655 <p>
657 </p>
658 </li>
659 <li>
660 <p>
662 </p>
663 </li>
664 <li>
665 <p>
666 rsync://host.xz/path/to/repo.git/
667 </p>
668 </li>
669 </ul></div>
670 <div class="para"><p>An alternative scp-like syntax may also be used with the ssh protocol:</p></div>
672 <li>
673 <p>
675 </p>
676 </li>
677 </ul></div>
678 <div class="para"><p>The ssh and git protocols additionally support ~username expansion:</p></div>
680 <li>
681 <p>
683 </p>
684 </li>
685 <li>
686 <p>
688 </p>
689 </li>
690 <li>
691 <p>
693 </p>
694 </li>
695 </ul></div>
697 syntaxes may be used:</p></div>
699 <li>
700 <p>
701 /path/to/repo.git/
702 </p>
703 </li>
704 <li>
705 <p>
706 file:///path/to/repo.git/
707 </p>
708 </li>
709 </ul></div>
712 details.</p></div>
715 exists. To explicitly request a remote helper, the following syntax
716 may be used:</p></div>
718 <li>
719 <p>
721 </p>
722 </li>
723 </ul></div>
725 URL-like string recognized by the specific remote helper being
728 you want to use a different format for them (such that the URLs you
729 use will be rewritten into URLs that work), you can create a
730 configuration section of the form:</p></div>
735 </div></div>
740 insteadOf = host.xz:/path/to/
741 insteadOf = work:</tt></pre>
742 </div></div>
746 configuration section of the form:</p></div>
751 </div></div>
756 pushInsteadOf = git://example.org/</tt></pre>
757 </div></div>
759 "ssh://example.org/path/to/repo.git" for pushes, but pulls will still
760 use the original URL.</p></div>
761 </div>
767 <li>
768 <p>
770 </p>
771 </li>
772 <li>
773 <p>
775 </p>
776 </li>
777 <li>
778 <p>
780 </p>
781 </li>
782 </ul></div>
784 because they each contain a refspec which git will use by default.</p></div>
785 <h3 id="_named_remote_in_configuration_file">Named remote in configuration file</h3><div style="clear:left"></div>
787 configured using <a href="git-remote.html">git-remote(1)</a>, <a href="git-config.html">git-config(1)</a>
789 this remote will be used to access the repository. The refspec
790 of this remote will be used by default when you do
791 not provide a refspec on the command line. The entry in the
792 config file would appear like this:</p></div>
800 </div></div>
801 <div class="para"><p>The <tt><pushurl></tt> is used for pushes only. It is optional and defaults
803 <h3 id="_named_file_in_tt_git_dir_remotes_tt">Named file in <tt>$GIT_DIR/remotes</tt></h3><div style="clear:left"></div>
806 in this file will be used to access the repository. The refspec
807 in this file will be used as default when you do not
808 provide a refspec on the command line. This file should have the
809 following format:</p></div>
812 <pre><tt> URL: one of the above URL format
815 </tt></pre>
816 </div></div>
820 be specified for additional branch mappings.</p></div>
821 <h3 id="_named_file_in_tt_git_dir_branches_tt">Named file in <tt>$GIT_DIR/branches</tt></h3><div style="clear:left"></div>
824 The URL in this file will be used to access the repository.
825 This file should have the following format:</p></div>
829 </div></div>
830 <div class="para"><p><tt><url></tt> is required; <tt>#<head></tt> is optional.</p></div>
832 refspecs, if you don't provide one on the command line.
839 </div></div>
844 </div></div>
845 </div>
849 <li>
850 <p>
851 Update the remote-tracking branches:
852 </p>
856 </div></div>
858 namespace and stores them to the local refs/remotes/origin/ namespace,
860 refspec.</p></div>
861 </li>
862 <li>
863 <p>
864 Using refspecs explicitly:
865 </p>
869 </div></div>
870 <div class="para"><p>This updates (or creates, as necessary) branches <tt>pu</tt> and <tt>tmp</tt> in
871 the local repository by fetching from the branches (respectively)
873 <div class="para"><p>The <tt>pu</tt> branch will be updated even if it is does not fast-forward,
875 </li>
876 </ul></div>
877 </div>
881 </div>
886 </div>
889 <div class="para"><p>Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.</p></div>
890 </div>
894 </div>
898 </div>
899 </div>
900 </body>
901 </html>