| blob | 0ebb54f84bb9d35c9f082af60e4b4616fdddd528 |
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-clone(1) Manual Page
407 </h1>
410 <p>git-clone -
411 Clone a repository into a new directory
412 </p>
413 </div>
414 </div>
419 [-l] [-s] [--no-hardlinks] [-q] [-n] [--bare] [--mirror]
424 </div></div>
425 </div>
429 remote-tracking branches for each branch in the cloned repository
431 initial branch that is forked from the cloned repository’s
432 currently active branch.</p></div>
433 <div class="paragraph"><p>After the clone, a plain <tt>git fetch</tt> without arguments will update
435 arguments will in addition merge the remote master branch into the
436 current master branch, if any.</p></div>
440 configuration variables.</p></div>
441 </div>
446 --local
447 </dt>
449 -l
450 </dt>
451 <dd>
452 <p>
453 When the repository to clone from is on a local machine,
454 this flag bypasses the normal "git aware" transport
455 mechanism and clones the repository by making a copy of
456 HEAD and everything under objects and refs directories.
458 to save space when possible. This is now the default when
460 syntax, so it essentially is a no-op option. To force
461 copying instead of hardlinking (which may be desirable
462 if you are trying to make a back-up of your repository),
463 but still avoid the usual "git aware" transport
465 </p>
466 </dd>
468 --no-hardlinks
469 </dt>
470 <dd>
471 <p>
472 Optimize the cloning process from a repository on a
474 directory.
475 </p>
476 </dd>
478 --shared
479 </dt>
481 -s
482 </dt>
483 <dd>
484 <p>
485 When the repository to clone is on the local machine,
486 instead of using hard links, automatically setup
488 with the source repository. The resulting repository
489 starts out without any object of its own.
490 </p>
491 <div class="paragraph"><p><strong>NOTE</strong>: this is a possibly dangerous operation; do <strong>not</strong> use
492 it unless you understand what it does. If you clone your
493 repository using this option and then delete branches (or use any
494 other git command that makes any existing commit unreferenced) in the
495 source repository, some objects may become unreferenced (or dangling).
498 If these objects are removed and were referenced by the cloned repository,
499 then the cloned repository will become corrupt.</p></div>
500 <div class="paragraph"><p>Note that running <tt>git repack</tt> without the <tt>-l</tt> option in a repository
504 default.</p></div>
505 <div class="paragraph"><p>If you want to break the dependency of a repository cloned with <tt>-s</tt> on
507 objects from the source repository into a pack in the cloned repository.</p></div>
508 </dd>
511 </dt>
512 <dd>
513 <p>
514 If the reference repository is on the local machine,
516 obtain objects from the reference repository. Using
517 an already existing repository as an alternate will
518 require fewer objects to be copied from the repository
519 being cloned, reducing network and local storage costs.
520 </p>
521 <div class="paragraph"><p><strong>NOTE</strong>: see the NOTE for the <tt>--shared</tt> option.</p></div>
522 </dd>
524 --quiet
525 </dt>
527 -q
528 </dt>
529 <dd>
530 <p>
531 Operate quietly. Progress is not reported to the standard
533 command when given.
534 </p>
535 </dd>
537 --verbose
538 </dt>
540 -v
541 </dt>
542 <dd>
543 <p>
544 Run verbosely. Does not affect the reporting of progress status
545 to the standard error stream.
546 </p>
547 </dd>
549 --progress
550 </dt>
551 <dd>
552 <p>
553 Progress status is reported on the standard error stream
554 by default when it is attached to a terminal, unless -q
555 is specified. This flag forces progress status even if the
556 standard error stream is not directed to a terminal.
557 </p>
558 </dd>
560 --no-checkout
561 </dt>
563 -n
564 </dt>
565 <dd>
566 <p>
567 No checkout of HEAD is performed after the clone is complete.
568 </p>
569 </dd>
571 --bare
572 </dt>
573 <dd>
574 <p>
579 because there is nowhere to check out the working tree.
580 Also the branch heads at the remote are copied directly
581 to corresponding local branch heads, without mapping
583 used, neither remote-tracking branches nor the related
584 configuration variables are created.
585 </p>
586 </dd>
588 --mirror
589 </dt>
590 <dd>
591 <p>
594 source to local branches of the target, it maps all refs (including
595 remote-tracking branches, notes etc.) and sets up a refspec configuration such
597 target repository.
598 </p>
599 </dd>
602 </dt>
605 </dt>
606 <dd>
607 <p>
610 </p>
611 </dd>
614 </dt>
617 </dt>
618 <dd>
619 <p>
620 Instead of pointing the newly created HEAD to the branch pointed
622 instead. In a non-bare repository, this is the branch that will
623 be checked out.
624 </p>
625 </dd>
628 </dt>
631 </dt>
632 <dd>
633 <p>
634 When given, and the repository to clone from is accessed
635 via ssh, this specifies a non-default path for the command
636 run on the other end.
637 </p>
638 </dd>
641 </dt>
642 <dd>
643 <p>
644 Specify the directory from which templates will be used;
646 </p>
647 </dd>
650 </dt>
651 <dd>
652 <p>
654 specified number of revisions. A shallow repository has a
655 number of limitations (you cannot clone or fetch from
656 it, nor push from nor into it), but is adequate if you
657 are only interested in the recent history of a large project
658 with a long history, and would want to send in fixes
659 as patches.
660 </p>
661 </dd>
663 --recursive
664 </dt>
666 --recurse-submodules
667 </dt>
668 <dd>
669 <p>
670 After the clone is created, initialize all submodules within,
671 using their default settings. This is equivalent to running
673 the clone is finished. This option is ignored if the cloned
674 repository does not have a worktree/checkout (i.e. if any of
676 </p>
677 </dd>
680 </dt>
681 <dd>
682 <p>
683 The (possibly remote) repository to clone from. See the
685 repositories.
686 </p>
687 </dd>
690 </dt>
691 <dd>
692 <p>
693 The name of a new directory to clone into. The "humanish"
694 part of the source repository is used if no directory is
697 is only allowed if the directory is empty.
698 </p>
699 </dd>
700 </dl></div>
701 </div>
704 <div class="paragraph"><p>In general, URLs contain information about the transport protocol, the
705 address of the remote server, and the path to the repository.
706 Depending on the transport protocol, some of this information may be
707 absent.</p></div>
709 protocols. The following syntaxes may be used with them:</p></div>
711 <li>
712 <p>
714 </p>
715 </li>
716 <li>
717 <p>
719 </p>
720 </li>
721 <li>
722 <p>
724 </p>
725 </li>
726 <li>
727 <p>
729 </p>
730 </li>
731 <li>
732 <p>
733 rsync://host.xz/path/to/repo.git/
734 </p>
735 </li>
736 </ul></div>
737 <div class="paragraph"><p>An alternative scp-like syntax may also be used with the ssh protocol:</p></div>
739 <li>
740 <p>
742 </p>
743 </li>
744 </ul></div>
745 <div class="paragraph"><p>The ssh and git protocols additionally support ~username expansion:</p></div>
747 <li>
748 <p>
750 </p>
751 </li>
752 <li>
753 <p>
755 </p>
756 </li>
757 <li>
758 <p>
760 </p>
761 </li>
762 </ul></div>
764 syntaxes may be used:</p></div>
766 <li>
767 <p>
768 /path/to/repo.git/
769 </p>
770 </li>
771 <li>
772 <p>
774 </p>
775 </li>
776 </ul></div>
778 --local option.</p></div>
779 <div class="paragraph"><p>When git doesn’t know how to handle a certain transport protocol, it
781 exists. To explicitly request a remote helper, the following syntax
782 may be used:</p></div>
784 <li>
785 <p>
787 </p>
788 </li>
789 </ul></div>
790 <div class="paragraph"><p>where <address> may be a path, a server and path, or an arbitrary
791 URL-like string recognized by the specific remote helper being
793 <div class="paragraph"><p>If there are a large number of similarly-named remote repositories and
794 you want to use a different format for them (such that the URLs you
795 use will be rewritten into URLs that work), you can create a
796 configuration section of the form:</p></div>
801 </div></div>
806 insteadOf = host.xz:/path/to/
807 insteadOf = work:</tt></pre>
808 </div></div>
809 <div class="paragraph"><p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
812 configuration section of the form:</p></div>
817 </div></div>
822 pushInsteadOf = git://example.org/</tt></pre>
823 </div></div>
825 "ssh://example.org/path/to/repo.git" for pushes, but pulls will still
826 use the original URL.</p></div>
827 </div>
831 <li>
832 <p>
833 Clone from upstream:
834 </p>
838 $ cd my2.6
839 $ make</tt></pre>
840 </div></div>
841 </li>
842 <li>
843 <p>
844 Make a local clone that borrows from the current directory, without checking things out:
845 </p>
848 <pre><tt>$ git clone -l -s -n . ../copy
849 $ cd ../copy
850 $ git show-branch</tt></pre>
851 </div></div>
852 </li>
853 <li>
854 <p>
855 Clone from upstream while borrowing from an existing local directory:
856 </p>
859 <pre><tt>$ git clone --reference my2.6 \
860 git://git.kernel.org/pub/scm/.../linux-2.7 \
861 my2.7
862 $ cd my2.7</tt></pre>
863 </div></div>
864 </li>
865 <li>
866 <p>
867 Create a bare repository to publish your changes to the public:
868 </p>
872 </div></div>
873 </li>
874 <li>
875 <p>
876 Create a repository on the kernel.org machine that borrows from Linus:
877 </p>
882 </div></div>
883 </li>
884 </ul></div>
885 </div>
889 </div>
893 </div>
894 </div>
895 </body>
896 </html>