| blob | 97ecbcf6b1d6131972d060381612caad91f5b2d8 |
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-bundle(1) Manual Page
313 </h1>
316 <p>git-bundle -
317 Move objects and refs by archive
318 </p>
319 </div>
320 </div>
328 </div>
332 machine be replicated on another machine, but the two machines cannot
333 be directly connected, and therefore the interactive git protocols (git,
334 ssh, rsync, http) cannot be used. This command provides support for
336 in an archive at the originating machine, then importing those into
338 after moving the archive by some means (i.e., by sneakernet). As no
339 direct connection between the repositories exists, the user must specify a
340 basis for the bundle that is held by the destination repository: the
341 bundle assumes that all objects in the basis are already in the
342 destination repository.</p></div>
343 </div>
347 <dt>
349 </dt>
350 <dd>
351 <p>
354 </p>
355 </dd>
356 <dt>
358 </dt>
359 <dd>
360 <p>
361 Used to check that a bundle file is valid and will apply
362 cleanly to the current repository. This includes checks on the
363 bundle format itself as well as checking that the prerequisite
364 commits exist and are fully linked in the current repository.
366 with a non-zero status.
367 </p>
368 </dd>
369 <dt>
371 </dt>
372 <dd>
373 <p>
374 Lists the references defined in the bundle. If followed by a
375 list of references, only references matching those given are
376 printed out.
377 </p>
378 </dd>
379 <dt>
381 </dt>
382 <dd>
383 <p>
385 for storage in the repository, then prints the names of all
386 defined references. If a list of references is given, only
387 references matching those in the list are printed. This command is
389 </p>
390 </dd>
391 <dt>
392 [git-rev-list-args…]
393 </dt>
394 <dd>
395 <p>
399 current master reference to be packaged along with all objects
400 added since its 10th ancestor commit. There is no explicit
401 limit to the number of references and objects that may be
402 packaged.
403 </p>
404 </dd>
405 <dt>
406 [refname…]
407 </dt>
408 <dd>
409 <p>
410 A list of references used to limit the references reported as
412 expects to receive only those references asked for and not
415 </p>
416 </dd>
417 </dl></div>
418 </div>
424 defining the basis. More than one reference may be packaged, and more
425 than one basis can be specified. The objects packaged are those not
426 contained in the union of the given bases. Each basis can be
430 It is okay to err on the side of caution, causing the bundle file
431 to contain objects already in the destination, as these are ignored
432 when unpacking at the destination.</p></div>
433 </div>
437 to another repository R2 on machine B.
438 For whatever reason, direct connection between A and B is not allowed,
439 but we can move data from A to B via some mechanism (CD, email, etc.).
440 We want to update R2 with development made on the branch master in R1.</p></div>
442 any basis. You can use a tag to remember up to what commit you last
443 processed, in order to make it easy to later update the other repository
444 with an incremental bundle:</p></div>
447 <pre><tt>machineA$ cd R1
448 machineA$ git bundle create file.bundle master
449 machineA$ git tag -f lastR2bundle master</tt></pre>
450 </div></div>
452 the repository on machine B, then you can clone from the bundle as if it
453 were a remote repository instead of creating an empty repository and then
454 pulling or fetching objects from the bundle:</p></div>
458 </div></div>
460 lets you fetch and pull from the bundle. The $GIT_DIR/config file in R2 will
461 have an entry like this:</p></div>
465 url = /home/me/tmp/file.bundle
466 fetch = refs/heads/*:refs/remotes/origin/*</tt></pre>
467 </div></div>
469 replacing the bundle stored at /home/me/tmp/file.bundle with incremental
470 updates.</p></div>
472 incremental bundle to update the other repository:</p></div>
475 <pre><tt>machineA$ cd R1
476 machineA$ git bundle create file.bundle lastR2bundle..master
477 machineA$ git tag -f lastR2bundle master</tt></pre>
478 </div></div>
480 /home/me/tmp/file.bundle, and pull from it.</p></div>
483 <pre><tt>machineB$ cd R2
484 machineB$ git pull</tt></pre>
485 </div></div>
487 have the necessary objects, you can use that knowledge to specify the
488 basis, giving a cut-off point to limit the revisions and objects that go
489 in the resulting bundle. The previous example used lastR2bundle tag
490 for this purpose, but you can use any other options that you would give to
496 </div></div>
501 </div></div>
506 </div></div>
507 <div class="para"><p>You can run <tt>git-bundle verify</tt> to see if you can extract from a bundle
508 that was created with a basis:</p></div>
512 </div></div>
514 bundle and will error out if you do not have them.</p></div>
516 regular repository which it fetches or pulls from. You can, for example, map
517 references when fetching:</p></div>
521 </div></div>
526 </div></div>
527 </div>
531 </div>
535 </div>
539 </div>
540 </div>
541 </body>
542 </html>