Autogenerated HTML docs for v1.6.5.2-74-g610f9

1 files changed, 5 insertions, 4 deletions

diff --git a/git-fsck.html b/git-fsck.html
index 4128a4632..03dfd0848 100644
--- a/git-fsck.html
+++ b/git-fsck.html
@@ -322,7 +322,7 @@ git-fsck(1) Manual Page
 <div class="sectionbody">

 <div class="verseblock">

 <div class="content"><em>git fsck</em> [--tags] [--root] [--unreachable] [--cache] [--no-reflogs]

-         [--full] [--strict] [--verbose] [--lost-found] [&lt;object&gt;*]</div></div>

+         [--[no-]full] [--strict] [--verbose] [--lost-found] [&lt;object&gt;*]</div></div>

 </div>

 <h2 id="_description">DESCRIPTION</h2>

 <div class="sectionbody">

@@ -398,7 +398,8 @@ index file, all SHA1 references in .git/refs/*, and all reflogs (unless
         or $GIT_DIR/objects/info/alternates,

         and in packed git archives found in $GIT_DIR/objects/pack

         and corresponding pack subdirectories in alternate

-        object pools.

+        object pools.  This is now default; you can turn it off

+        with --no-full.

 </p>

 </dd>

 <dt>

@@ -445,7 +446,7 @@ that aren't readable from any of the specified head nodes.</p></div>
 <pre><tt>git fsck --unreachable HEAD \

         $(git for-each-ref --format="%(objectname)" refs/heads)</tt></pre>

 </div></div>

-<div class="para"><p>will do quite a _lot_ of verification on the tree. There are a few

+<div class="para"><p>will do quite a <em>lot</em> of verification on the tree. There are a few

 extra validity tests to be added (make sure that tree objects are

 sorted properly etc), but on the whole if <em>git-fsck</em> is happy, you

 do have a valid tree.</p></div>

@@ -571,7 +572,7 @@ GIT_ALTERNATE_OBJECT_DIRECTORIES
 </div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2009-07-01 02:30:51 UTC

+Last updated 2009-10-26 05:16:28 UTC

 </div>

 </div>

 </body>