| blob | a091868d530f588a81a69a5841944c7378555c3e |
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-bundle(1) Manual Page
574 </h1>
577 <p>git-bundle -
578 Move objects and refs by archive
579 </p>
580 </div>
581 </div>
586 <div class="verseblock-content"><em>git bundle</em> create <file> <git-rev-list-args>
591 </div></div>
592 </div>
595 <div class="paragraph"><p>Some workflows require that one or more branches of development on one
596 machine be replicated on another machine, but the two machines cannot
597 be directly connected, and therefore the interactive git protocols (git,
598 ssh, rsync, http) cannot be used. This command provides support for
600 in an archive at the originating machine, then importing those into
602 after moving the archive by some means (e.g., by sneakernet). As no
603 direct connection between the repositories exists, the user must specify a
604 basis for the bundle that is held by the destination repository: the
605 bundle assumes that all objects in the basis are already in the
606 destination repository.</p></div>
607 </div>
613 </dt>
614 <dd>
615 <p>
618 </p>
619 </dd>
622 </dt>
623 <dd>
624 <p>
625 Used to check that a bundle file is valid and will apply
626 cleanly to the current repository. This includes checks on the
627 bundle format itself as well as checking that the prerequisite
628 commits exist and are fully linked in the current repository.
630 with a non-zero status.
631 </p>
632 </dd>
635 </dt>
636 <dd>
637 <p>
638 Lists the references defined in the bundle. If followed by a
639 list of references, only references matching those given are
640 printed out.
641 </p>
642 </dd>
645 </dt>
646 <dd>
647 <p>
649 for storage in the repository, then prints the names of all
650 defined references. If a list of references is given, only
651 references matching those in the list are printed. This command is
653 </p>
654 </dd>
657 </dt>
658 <dd>
659 <p>
662 below), that specifies the specific objects and references
664 current master reference to be packaged along with all objects
665 added since its 10th ancestor commit. There is no explicit
666 limit to the number of references and objects that may be
667 packaged.
668 </p>
669 </dd>
672 </dt>
673 <dd>
674 <p>
675 A list of references used to limit the references reported as
677 expects to receive only those references asked for and not
680 </p>
681 </dd>
682 </dl></div>
683 </div>
689 defining the basis. More than one reference may be packaged, and more
690 than one basis can be specified. The objects packaged are those not
691 contained in the union of the given bases. Each basis can be
695 It is okay to err on the side of caution, causing the bundle file
696 to contain objects already in the destination, as these are ignored
697 when unpacking at the destination.</p></div>
698 </div>
701 <div class="paragraph"><p>Assume you want to transfer the history from a repository R1 on machine A
702 to another repository R2 on machine B.
703 For whatever reason, direct connection between A and B is not allowed,
704 but we can move data from A to B via some mechanism (CD, email, etc.).
705 We want to update R2 with development made on the branch master in R1.</p></div>
706 <div class="paragraph"><p>To bootstrap the process, you can first create a bundle that does not have
707 any basis. You can use a tag to remember up to what commit you last
708 processed, in order to make it easy to later update the other repository
709 with an incremental bundle:</p></div>
712 <pre><tt>machineA$ cd R1
713 machineA$ git bundle create file.bundle master
714 machineA$ git tag -f lastR2bundle master</tt></pre>
715 </div></div>
716 <div class="paragraph"><p>Then you transfer file.bundle to the target machine B. If you are creating
717 the repository on machine B, then you can clone from the bundle as if it
718 were a remote repository instead of creating an empty repository and then
719 pulling or fetching objects from the bundle:</p></div>
723 </div></div>
724 <div class="paragraph"><p>This will define a remote called "origin" in the resulting repository that
725 lets you fetch and pull from the bundle. The $GIT_DIR/config file in R2 will
726 have an entry like this:</p></div>
730 url = /home/me/tmp/file.bundle
731 fetch = refs/heads/*:refs/remotes/origin/*</tt></pre>
732 </div></div>
733 <div class="paragraph"><p>To update the resulting mine.git repository, you can fetch or pull after
734 replacing the bundle stored at /home/me/tmp/file.bundle with incremental
735 updates.</p></div>
737 incremental bundle to update the other repository:</p></div>
740 <pre><tt>machineA$ cd R1
741 machineA$ git bundle create file.bundle lastR2bundle..master
742 machineA$ git tag -f lastR2bundle master</tt></pre>
743 </div></div>
745 /home/me/tmp/file.bundle, and pull from it.</p></div>
748 <pre><tt>machineB$ cd R2
749 machineB$ git pull</tt></pre>
750 </div></div>
751 <div class="paragraph"><p>If you know up to what commit the intended recipient repository should
752 have the necessary objects, you can use that knowledge to specify the
753 basis, giving a cut-off point to limit the revisions and objects that go
754 in the resulting bundle. The previous example used the lastR2bundle tag
755 for this purpose, but you can use any other options that you would give to
761 </div></div>
766 </div></div>
771 </div></div>
772 <div class="paragraph"><p>You can run <tt>git-bundle verify</tt> to see if you can extract from a bundle
773 that was created with a basis:</p></div>
777 </div></div>
778 <div class="paragraph"><p>This will list what commits you must have in order to extract from the
779 bundle and will error out if you do not have them.</p></div>
780 <div class="paragraph"><p>A bundle from a recipient repository’s point of view is just like a
781 regular repository which it fetches or pulls from. You can, for example, map
782 references when fetching:</p></div>
786 </div></div>
791 </div></div>
792 </div>
796 </div>
797 </div>
802 </div>
803 </div>
804 </body>
805 </html>