summaryrefslogtreecommitdiffstats
path: root/git-fsck.html
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2011-12-22 12:21:44 -0800
committerJunio C Hamano <gitster@pobox.com>2011-12-22 12:21:44 -0800
commit962f3a392a5b5c3f552a403dcc58d9f1eae2a930 (patch)
tree801a063b399de3fc30ed779874d6aa1a0da042ad /git-fsck.html
parent0df9271a3b43155a867f5785c830fb58860b2a6e (diff)
downloadgit-htmldocs-962f3a392a5b5c3f552a403dcc58d9f1eae2a930.tar.gz
Autogenerated HTML docs for v1.7.8.1-362-g5d6df
Diffstat (limited to 'git-fsck.html')
-rw-r--r--git-fsck.html27
1 files changed, 9 insertions, 18 deletions
diff --git a/git-fsck.html b/git-fsck.html
index d5793fa8d..5b1a135db 100644
--- a/git-fsck.html
+++ b/git-fsck.html
@@ -715,27 +715,18 @@ index file, all SHA1 references in .git/refs/*, and all reflogs (unless
</p>
</dd>
</dl></div>
-<div class="paragraph"><p>It tests SHA1 and general object sanity, and it does full tracking of
-the resulting reachability and everything else. It prints out any
+</div>
+<h2 id="_discussion">DISCUSSION</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>git-fsck tests SHA1 and general object sanity, and it does full tracking
+of the resulting reachability and everything else. It prints out any
corruption it finds (missing or bad objects), and if you use the
-<em>--unreachable</em> flag it will also print out objects that exist but
-that aren&#8217;t reachable from any of the specified head nodes.</p></div>
-<div class="paragraph"><p>So for example</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><tt>git fsck --unreachable HEAD \
- $(git for-each-ref --format="%(objectname)" refs/heads)</tt></pre>
-</div></div>
-<div class="paragraph"><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>
+<em>--unreachable</em> flag it will also print out objects that exist but that
+aren&#8217;t reachable from any of the specified head nodes (or the default
+set, as mentioned above).</p></div>
<div class="paragraph"><p>Any corrupt objects you will have to find in backups or other archives
(i.e., you can just remove them and do an <em>rsync</em> with some other site in
the hopes that somebody else has the object you have corrupted).</p></div>
-<div class="paragraph"><p>Of course, "valid tree" doesn&#8217;t mean that it wasn&#8217;t generated by some
-evil person, and the end result might be crap. git is a revision
-tracking system, not a quality assurance system ;)</p></div>
</div>
<h2 id="_extracted_diagnostics">Extracted Diagnostics</h2>
<div class="sectionbody">
@@ -838,7 +829,7 @@ GIT_ALTERNATE_OBJECT_DIRECTORIES
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2011-12-06 16:26:11 PDT
+Last updated 2011-12-22 12:21:20 PDT
</div>
</div>
</body>