Autogenerated HTML docs for v1.5.6.1-156-ge903b

1 files changed, 21 insertions, 22 deletions

diff --git a/git-bundle.html b/git-bundle.html
index 8fafa5859..3ec368b7e 100644
--- a/git-bundle.html
+++ b/git-bundle.html
@@ -273,10 +273,10 @@ git-bundle(1) Manual Page
 <h2>SYNOPSIS</h2>

 <div class="sectionbody">

 <div class="verseblock">

-<div class="content"><em>git-bundle</em> create &lt;file&gt; &lt;git-rev-list args&gt;

-<em>git-bundle</em> verify &lt;file&gt;

-<em>git-bundle</em> list-heads &lt;file&gt; [refname&#8230;]

-<em>git-bundle</em> unbundle &lt;file&gt; [refname&#8230;]</div></div>

+<div class="content"><em>git bundle</em> create &lt;file&gt; &lt;git-rev-list args&gt;

+<em>git bundle</em> verify &lt;file&gt;

+<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>

 <div class="sectionbody">

@@ -284,9 +284,9 @@ git-bundle(1) Manual Page
 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

-git-fetch and git-pull to operate by packaging objects and references

+<tt>git-fetch</tt> and <tt>git-pull</tt> to operate by packaging objects and references

 in an archive at the originating machine, then importing those into

-another repository using <a href="git-fetch.html">git-fetch(1)</a> and <a href="git-pull.html">git-pull(1)</a>

+another repository using <tt>git-fetch</tt> and <tt>git-pull</tt>

 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

@@ -302,7 +302,7 @@ create &lt;file&gt;
 <dd>

 <p>

        Used to create a bundle named <em>file</em>.  This requires the

-       git-rev-list arguments to define the bundle contents.

+       <tt>git-rev-list</tt> arguments to define the bundle contents.

 </p>

 </dd>

 <dt>

@@ -314,7 +314,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.

-       git-bundle prints a list of missing commits, if any, and exits

+       <tt>git-bundle</tt> prints a list of missing commits, if any, and exits

        with non-zero status.

 </p>

 </dd>

@@ -333,12 +333,11 @@ unbundle &lt;file&gt;
 </dt>

 <dd>

 <p>

-       Passes the objects in the bundle to <a href="git-index-pack.html">git-index-pack(1)</a>

+       Passes the objects in the bundle to <tt>git-index-pack</tt>

        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

-       <a href="git-fetch.html">git-fetch(1)</a>.

+       really plumbing, intended to be called only by <tt>git-fetch</tt>.

 </p>

 </dd>

 <dt>

@@ -346,8 +345,8 @@ unbundle &lt;file&gt;
 </dt>

 <dd>

 <p>

-       A list of arguments, acceptable to git-rev-parse and

-       git-rev-list, that specify the specific objects and references

+       A list of arguments, acceptable to <tt>git-rev-parse</tt> and

+       <tt>git-rev-list</tt>, 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

@@ -361,18 +360,18 @@ unbundle &lt;file&gt;
 <dd>

 <p>

        A list of references used to limit the references reported as

-       available. This is principally of use to git-fetch, which

+       available. This is principally of use to <tt>git-fetch</tt>, which

        expects to receive only those references asked for and not

-       necessarily everything in the pack (in this case, git-bundle is

-       acting like <a href="git-fetch-pack.html">git-fetch-pack(1)</a>).

+       necessarily everything in the pack (in this case, <tt>git-bundle</tt> is

+       acting like <tt>git-fetch-pack</tt>).

 </p>

 </dd>

 </dl>

 </div>

 <h2>SPECIFYING REFERENCES</h2>

 <div class="sectionbody">

-<p>git-bundle will only package references that are shown by

-git-show-ref: this includes heads, tags, and remote heads.  References

+<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

 defining the basis.  More than one reference may be packaged, and more

 than one basis can be specified.  The objects packaged are those not

@@ -414,7 +413,7 @@ and move it afterwards to help build the bundle.</p>
 </ul>

 <div class="listingblock">

 <div class="content">

-<pre><tt>$ git-bundle create mybundle master ^lastR2bundle

+<pre><tt>$ git bundle create mybundle master ^lastR2bundle

 $ git tag -f lastR2bundle master</tt></pre>

 </div></div>

 <ul>

@@ -453,8 +452,8 @@ With a limit on the number of commits
 <p>Then you move mybundle from A to B, and in R2 on B:</p>

 <div class="listingblock">

 <div class="content">

-<pre><tt>$ git-bundle verify mybundle

-$ git-fetch mybundle master:localRef</tt></pre>

+<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="listingblock">

@@ -484,7 +483,7 @@ network.</p>
 </div>

 <div id="footer">

 <div id="footer-text">

-Last updated 08-Jun-2008 01:33:22 UTC

+Last updated 02-Jul-2008 03:01:33 UTC

 </div>

 </div>

 </body>