Autogenerated HTML docs for v1.6.0.2-287-g3791f

1 files changed, 3 insertions, 3 deletions

diff --git a/git-filter-branch.html b/git-filter-branch.html
index 1ef716e92..467ed51ea 100644
--- a/git-filter-branch.html
+++ b/git-filter-branch.html
@@ -336,7 +336,7 @@ Those filters can modify each tree (e.g. removing a file or running
 a perl rewrite on all files) or information about each commit.

 Otherwise, all information (including original commit times or merge

 information) will be preserved.</p></div>

-<div class="para"><p>The command will only rewrite the <em>positive</em> refs mentioned in the

+<div class="para"><p>The command will only rewrite the _positive_ refs mentioned in the

 command line (e.g. if you pass <em>a..b</em>, only <em>b</em> will be rewritten).

 If you specify no filters, the commits will be recommitted without any

 changes, which would normally have no effect.  Nevertheless, this may be

@@ -629,7 +629,7 @@ point to the top-most revision that a <em>git-rev-list</em> of this range
 will print.</p></div>

 <div class="para"><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 <em>changes</em> together with the commits, you should use the

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

 interactive mode of <em>git-rebase</em>.</p></div>

 <div class="para"><p>Consider this history:</p></div>

 <div class="listingblock">

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

 <div id="footer">

 <div id="footer-text">

-Last updated 2008-08-10 03:55:19 UTC

+Last updated 2008-09-19 06:32:54 UTC

 </div>

 </div>

 </body>