Autogenerated HTML docs for v1.5.6.1-156-ge903b

1 files changed, 8 insertions, 8 deletions

diff --git a/git-filter-branch.html b/git-filter-branch.html
index 46e289f22..7cb33fa67 100644
--- a/git-filter-branch.html
+++ b/git-filter-branch.html
@@ -273,7 +273,7 @@ git-filter-branch(1) Manual Page
 <h2>SYNOPSIS</h2>

 <div class="sectionbody">

 <div class="verseblock">

-<div class="content"><em>git-filter-branch</em> [--env-filter &lt;command&gt;] [--tree-filter &lt;command&gt;]

+<div class="content"><em>git filter-branch</em> [--env-filter &lt;command&gt;] [--tree-filter &lt;command&gt;]

         [--index-filter &lt;command&gt;] [--parent-filter &lt;command&gt;]

         [--msg-filter &lt;command&gt;] [--commit-filter &lt;command&gt;]

         [--tag-name-filter &lt;command&gt;] [--subdirectory-filter &lt;directory&gt;]

@@ -369,7 +369,7 @@ multiple commits.</p>
         This is the filter for rewriting the commit's parent list.

         It will receive the parent string on stdin and shall output

         the new parent string on stdout.  The parent string is in

-        a format accepted by <a href="git-commit-tree.html">git-commit-tree(1)</a>: empty for

+        the format described in <a href="git-commit-tree.html">git-commit-tree(1)</a>: empty for

         the initial commit, "-p parent" for a normal commit and

         "-p parent1 -p parent2 -p parent3 &#8230;" for a merge commit.

 </p>

@@ -392,7 +392,7 @@ multiple commits.</p>
 <p>

         This is the filter for performing the commit.

         If this filter is specified, it will be called instead of the

-        <a href="git-commit-tree.html">git-commit-tree(1)</a> command, with arguments of the form

+        <tt>git-commit-tree</tt> command, with arguments of the form

         "&lt;TREE_ID&gt; [-p &lt;PARENT_COMMIT_ID&gt;]&#8230;" and the log message on

         stdin.  The commit id is expected on stdout.

 </p>

@@ -402,7 +402,7 @@ have all of them as parents.</p>
 <p>You can use the <em>map</em> convenience function in this filter, and other

 convenience functions, too.  For example, calling <em>skip_commit "$@"</em>

 will leave out the current commit (but not its changes! If you want

-that, use <a href="git-rebase.html">git-rebase(1)</a> instead).</p>

+that, use <tt>git-rebase</tt> instead).</p>

 </dd>

 <dt>

 --tag-name-filter &lt;command&gt;

@@ -481,7 +481,7 @@ to other tags will be rewritten to point to the underlying commit.</p>
 <dd>

 <p>

         When options are given after the new branch name, they will

-        be passed to <a href="git-rev-list.html">git-rev-list(1)</a>.  Only commits in the resulting

+        be passed to <tt>git-rev-list</tt>.  Only commits in the resulting

         output will be filtered, although the filtered commits can still

         reference parents which are outside of that set.

 </p>

@@ -568,12 +568,12 @@ be removed this way:</p>
 </div></div>

 <p>To restrict rewriting to only part of the history, specify a revision

 range in addition to the new branch name.  The new branch name will

-point to the top-most revision that a <em>git rev-list</em> of this range

+point to the top-most revision that a <tt>git-rev-list</tt> of this range

 will print.</p>

 <p><strong>NOTE</strong> the changes introduced by the commits, and which are not reverted

 by subsequent commits, will still be in the rewritten branch. If you want

 to throw out _changes_ together with the commits, you should use the

-interactive mode of <a href="git-rebase.html">git-rebase(1)</a>.</p>

+interactive mode of <tt>git-rebase</tt>.</p>

 <p>Consider this history:</p>

 <div class="listingblock">

 <div class="content">

@@ -617,7 +617,7 @@ and the git list &lt;git@vger.kernel.org&gt;</p>
 </div>

 <div id="footer">

 <div id="footer-text">

-Last updated 08-Jun-2008 22:46:37 UTC

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

 </div>

 </div>

 </body>