Autogenerated HTML docs for v1.5.6.2-212-g08b5

author: Junio C Hamano <junio@hera.kernel.org> 2008-07-06 05:20:31 +0000
committer: Junio C Hamano <junio@hera.kernel.org> 2008-07-06 05:20:31 +0000
commit: ba4b9286c25f18c7ebbb809ee5732a7810377ab6 (patch)
tree: 390507328a7564b65dc803683c34235700b97409 /git-bundle.html
parent: 05bf9c54a827e48b2b576488f5170a3490b5180e (diff)
download: git-htmldocs-ba4b9286c25f18c7ebbb809ee5732a7810377ab6.tar.gz
1 files changed, 112 insertions, 64 deletions
diff --git a/git-bundle.html b/git-bundle.html
index 3ec368b7e..0dedd9ca4 100644
--- a/git-bundle.html
+++ b/git-bundle.html
@@ -3,7 +3,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 7.0.2" />
+<meta name="generator" content="AsciiDoc 8.2.5" />
 <style type="text/css">
 /* Debug borders */
 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
@@ -16,8 +16,13 @@ body {
   margin: 1em 5% 1em 5%;
 }
 
-a { color: blue; }
-a:visited { color: fuchsia; }
+a {
+  color: blue;
+  text-decoration: underline;
+}
+a:visited {
+  color: fuchsia;
+}
 
 em {
   font-style: italic;
@@ -39,13 +44,18 @@ h1, h2, h3, h4, h5, h6 {
   line-height: 1.3;
 }
 
-h1 {
+h1, h2, h3 {
   border-bottom: 2px solid silver;
 }
 h2 {
-  border-bottom: 2px solid silver;
   padding-top: 0.5em;
 }
+h3 {
+  float: left;
+}
+h3 + * {
+  clear: left;
+}
 
 div.sectionbody {
   font-family: serif;
@@ -70,7 +80,7 @@ span#author {
   color: #527bbd;
   font-family: sans-serif;
   font-weight: bold;
-  font-size: 1.2em;
+  font-size: 1.1em;
 }
 span#email {
 }
@@ -139,6 +149,9 @@ div.sidebarblock > div.content {
   padding: 0.5em;
 }
 
+div.listingblock {
+  margin-right: 0%;
+}
 div.listingblock > div.content {
   border: 1px solid silver;
   background: #f4f4f4;
@@ -148,9 +161,13 @@ div.listingblock > div.content {
 div.quoteblock > div.content {
   padding-left: 2.0em;
 }
-div.quoteblock .attribution {
+
+div.attribution {
   text-align: right;
 }
+div.verseblock + div.attribution {
+  text-align: left;
+}
 
 div.admonitionblock .icon {
   vertical-align: top;
@@ -194,13 +211,12 @@ dd > *:first-child {
 ul, ol {
     list-style-position: outside;
 }
-ol.olist2 {
+div.olist2 ol {
   list-style-type: lower-alpha;
 }
 
 div.tableblock > table {
-  border-color: #527bbd;
-  border-width: 3px;
+  border: 3px solid #527bbd;
 }
 thead {
   font-family: sans-serif;
@@ -214,6 +230,9 @@ div.hlist {
   margin-top: 0.8em;
   margin-bottom: 0.8em;
 }
+div.hlist td {
+  padding-bottom: 5px;
+}
 td.hlist1 {
   vertical-align: top;
   font-style: italic;
@@ -226,7 +245,33 @@ td.hlist2 {
 @media print {
   div#footer-badges { display: none; }
 }
-include::./stylesheets/xhtml11-manpage.css[]
+
+div#toctitle {
+  color: #527bbd;
+  font-family: sans-serif;
+  font-size: 1.1em;
+  font-weight: bold;
+  margin-top: 1.0em;
+  margin-bottom: 0.1em;
+}
+
+div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
+  margin-top: 0;
+  margin-bottom: 0;
+}
+div.toclevel2 {
+  margin-left: 2em;
+  font-size: 0.9em;
+}
+div.toclevel3 {
+  margin-left: 4em;
+  font-size: 0.9em;
+}
+div.toclevel4 {
+  margin-left: 6em;
+  font-size: 0.9em;
+}
+include1::./stylesheets/xhtml11-manpage.css[]
 /* Workarounds for IE6's broken and incomplete CSS2. */
 
 div.sidebar-content {
@@ -255,6 +300,9 @@ div.exampleblock-content {
   border-left: 2px solid silver;
   padding-left: 0.5em;
 }
+
+/* IE6 sets dynamically generated links as visited. */
+div#toc a:visited { color: blue; }
 </style>
 <title>git-bundle(1)</title>
 </head>
@@ -278,31 +326,31 @@ git-bundle(1) Manual Page
 <em>git bundle</em> list-heads &lt;file&gt; [refname&#8230;]
 <em>git bundle</em> unbundle &lt;file&gt; [refname&#8230;]</div></div>
 </div>
-<h2>DESCRIPTION</h2>
+<h2 id="_description">DESCRIPTION</h2>
 <div class="sectionbody">
-<p>Some workflows require that one or more branches of development on one
+<div class="para"><p>Some workflows require that one or more branches of development on one
 machine be replicated on another machine, but the two machines cannot
 be directly connected so the interactive git protocols (git, ssh,
 rsync, http) cannot be used.  This command provides support for
-<tt>git-fetch</tt> and <tt>git-pull</tt> to operate by packaging objects and references
+<em>git-fetch</em> and <em>git-pull</em> to operate by packaging objects and references
 in an archive at the originating machine, then importing those into
-another repository using <tt>git-fetch</tt> and <tt>git-pull</tt>
+another repository using <em>git-fetch</em> and <em>git-pull</em>
 after moving the archive by some means (i.e., by sneakernet).  As no
 direct connection between repositories exists, the user must specify a
 basis for the bundle that is held by the destination repository: the
 bundle assumes that all objects in the basis are already in the
-destination repository.</p>
+destination repository.</p></div>
 </div>
-<h2>OPTIONS</h2>
+<h2 id="_options">OPTIONS</h2>
 <div class="sectionbody">
-<dl>
+<div class="vlist"><dl>
 <dt>
 create &lt;file&gt;
 </dt>
 <dd>
 <p>
        Used to create a bundle named <em>file</em>.  This requires the
-       <tt>git-rev-list</tt> arguments to define the bundle contents.
+       <em>git-rev-list</em> arguments to define the bundle contents.
 </p>
 </dd>
 <dt>
@@ -314,7 +362,7 @@ verify &lt;file&gt;
        cleanly to the current repository.  This includes checks on the
        bundle format itself as well as checking that the prerequisite
        commits exist and are fully linked in the current repository.
-       <tt>git-bundle</tt> prints a list of missing commits, if any, and exits
+       <em>git-bundle</em> prints a list of missing commits, if any, and exits
        with non-zero status.
 </p>
 </dd>
@@ -333,11 +381,11 @@ unbundle &lt;file&gt;
 </dt>
 <dd>
 <p>
-       Passes the objects in the bundle to <tt>git-index-pack</tt>
+       Passes the objects in the bundle to <em>git-index-pack</em>
        for storage in the repository, then prints the names of all
        defined references. If a reflist is given, only references
        matching those in the given list are printed. This command is
-       really plumbing, intended to be called only by <tt>git-fetch</tt>.
+       really plumbing, intended to be called only by <em>git-fetch</em>.
 </p>
 </dd>
 <dt>
@@ -345,8 +393,8 @@ unbundle &lt;file&gt;
 </dt>
 <dd>
 <p>
-       A list of arguments, acceptable to <tt>git-rev-parse</tt> and
-       <tt>git-rev-list</tt>, that specify the specific objects and references
+       A list of arguments, acceptable to <em>git-rev-parse</em> and
+       <em>git-rev-list</em>, that specify the specific objects and references
        to transport.  For example, "master~10..master" causes the
        current master reference to be packaged along with all objects
        added since its 10th ancestor commit.  There is no explicit
@@ -360,130 +408,130 @@ unbundle &lt;file&gt;
 <dd>
 <p>
        A list of references used to limit the references reported as
-       available. This is principally of use to <tt>git-fetch</tt>, which
+       available. This is principally of use to <em>git-fetch</em>, which
        expects to receive only those references asked for and not
-       necessarily everything in the pack (in this case, <tt>git-bundle</tt> is
-       acting like <tt>git-fetch-pack</tt>).
+       necessarily everything in the pack (in this case, <em>git-bundle</em> is
+       acting like <em>git-fetch-pack</em>).
 </p>
 </dd>
-</dl>
+</dl></div>
 </div>
-<h2>SPECIFYING REFERENCES</h2>
+<h2 id="_specifying_references">SPECIFYING REFERENCES</h2>
 <div class="sectionbody">
-<p><tt>git-bundle</tt> will only package references that are shown by
-<tt>git-show-ref</tt>: this includes heads, tags, and remote heads.  References
-such as master~1 cannot be packaged, but are perfectly suitable for
+<div class="para"><p><em>git-bundle</em> will only package references that are shown by
+<em>git-show-ref</em>: this includes heads, tags, and remote heads.  References
+such as master<sub>1 cannot be packaged, but are perfectly suitable for
 defining the basis.  More than one reference may be packaged, and more
 than one basis can be specified.  The objects packaged are those not
 contained in the union of the given bases.  Each basis can be
-specified explicitly (e.g., ^master~10), or implicitly (e.g.,
-master~10..master, master --since=10.days.ago).</p>
-<p>It is very important that the basis used be held by the destination.
+specified explicitly (e.g., ^master</sub>10), or implicitly (e.g.,
+master~10..master, master --since=10.days.ago).</p></div>
+<div class="para"><p>It is very important that the basis used be held by the destination.
 It is okay to err on the side of conservatism, causing the bundle file
 to contain objects already in the destination as these are ignored
-when unpacking at the destination.</p>
+when unpacking at the destination.</p></div>
 </div>
-<h2>EXAMPLE</h2>
+<h2 id="_example">EXAMPLE</h2>
 <div class="sectionbody">
-<p>Assume two repositories exist as R1 on machine A, and R2 on machine B.
+<div class="para"><p>Assume two repositories exist as R1 on machine A, and R2 on machine B.
 For whatever reason, direct connection between A and B is not allowed,
 but we can move data from A to B via some mechanism (CD, email, etc).
-We want to update R2 with developments made on branch master in R1.</p>
-<p>To create the bundle you have to specify the basis. You have some options:</p>
-<ul>
+We want to update R2 with developments made on branch master in R1.</p></div>
+<div class="para"><p>To create the bundle you have to specify the basis. You have some options:</p></div>
+<div class="ilist"><ul>
 <li>
 <p>
 Without basis.
 </p>
-<p>This is useful when sending the whole history.</p>
+<div class="para"><p>This is useful when sending the whole history.</p></div>
 </li>
-</ul>
+</ul></div>
 <div class="listingblock">
 <div class="content">
 <pre><tt>$ git bundle create mybundle master</tt></pre>
 </div></div>
-<ul>
+<div class="ilist"><ul>
 <li>
 <p>
 Using temporally tags.
 </p>
-<p>We set a tag in R1 (lastR2bundle) after the previous such transport,
-and move it afterwards to help build the bundle.</p>
+<div class="para"><p>We set a tag in R1 (lastR2bundle) after the previous such transport,
+and move it afterwards to help build the bundle.</p></div>
 </li>
-</ul>
+</ul></div>
 <div class="listingblock">
 <div class="content">
 <pre><tt>$ git bundle create mybundle master ^lastR2bundle
 $ git tag -f lastR2bundle master</tt></pre>
 </div></div>
-<ul>
+<div class="ilist"><ul>
 <li>
 <p>
 Using a tag present in both repositories
 </p>
 </li>
-</ul>
+</ul></div>
 <div class="listingblock">
 <div class="content">
 <pre><tt>$ git bundle create mybundle master ^v1.0.0</tt></pre>
 </div></div>
-<ul>
+<div class="ilist"><ul>
 <li>
 <p>
 A basis based on time.
 </p>
 </li>
-</ul>
+</ul></div>
 <div class="listingblock">
 <div class="content">
 <pre><tt>$ git bundle create mybundle master --since=10.days.ago</tt></pre>
 </div></div>
-<ul>
+<div class="ilist"><ul>
 <li>
 <p>
 With a limit on the number of commits
 </p>
 </li>
-</ul>
+</ul></div>
 <div class="listingblock">
 <div class="content">
 <pre><tt>$ git bundle create mybundle master -n 10</tt></pre>
 </div></div>
-<p>Then you move mybundle from A to B, and in R2 on B:</p>
+<div class="para"><p>Then you move mybundle from A to B, and in R2 on B:</p></div>
 <div class="listingblock">
 <div class="content">
 <pre><tt>$ git bundle verify mybundle
 $ git fetch mybundle master:localRef</tt></pre>
 </div></div>
-<p>With something like this in the config in R2:</p>
+<div class="para"><p>With something like this in the config in R2:</p></div>
 <div class="listingblock">
 <div class="content">
 <pre><tt>[remote "bundle"]
     url = /home/me/tmp/file.bdl
     fetch = refs/heads/*:refs/remotes/origin/*</tt></pre>
 </div></div>
-<p>You can first sneakernet the bundle file to ~/tmp/file.bdl and
-then these commands on machine B:</p>
+<div class="para"><p>You can first sneakernet the bundle file to ~/tmp/file.bdl and
+then these commands on machine B:</p></div>
 <div class="listingblock">
 <div class="content">
 <pre><tt>$ git ls-remote bundle
 $ git fetch bundle
 $ git pull bundle</tt></pre>
 </div></div>
-<p>would treat it as if it is talking with a remote side over the
-network.</p>
+<div class="para"><p>would treat it as if it is talking with a remote side over the
+network.</p></div>
 </div>
-<h2>Author</h2>
+<h2 id="_author">Author</h2>
 <div class="sectionbody">
-<p>Written by Mark Levedahl &lt;mdl123@verizon.net&gt;</p>
+<div class="para"><p>Written by Mark Levedahl &lt;mdl123@verizon.net&gt;</p></div>
 </div>
-<h2>GIT</h2>
+<h2 id="_git">GIT</h2>
 <div class="sectionbody">
-<p>Part of the <a href="git.html">git(1)</a> suite</p>
+<div class="para"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 02-Jul-2008 03:01:33 UTC
+Last updated 2008-07-06 05:16:36 UTC
 </div>
 </div>
 </body>
author	Junio C Hamano <junio@hera.kernel.org>	2008-07-06 05:20:31 +0000
committer	Junio C Hamano <junio@hera.kernel.org>	2008-07-06 05:20:31 +0000
commit	ba4b9286c25f18c7ebbb809ee5732a7810377ab6 (patch)
tree	390507328a7564b65dc803683c34235700b97409 /git-bundle.html
parent	05bf9c54a827e48b2b576488f5170a3490b5180e (diff)
download	git-htmldocs-ba4b9286c25f18c7ebbb809ee5732a7810377ab6.tar.gz