diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2008-07-02 03:06:38 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2008-07-02 03:06:38 +0000 |
| commit | fce7c7e1549d1a2a2b0faf5952378236eed4d468 (patch) | |
| tree | ffce2ae419b52786a0e567f4fddaadd89016f62c /git-fsck.html | |
| parent | bb8e996adf4293a0b624fe77e95e12ae8d1faed9 (diff) | |
| download | git-htmldocs-fce7c7e1549d1a2a2b0faf5952378236eed4d468.tar.gz | |
Autogenerated HTML docs for v1.5.6.1-156-ge903b
Diffstat (limited to 'git-fsck.html')
| -rw-r--r-- | git-fsck.html | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/git-fsck.html b/git-fsck.html index 751a5ad19..95657d08c 100644 --- a/git-fsck.html +++ b/git-fsck.html @@ -273,7 +273,7 @@ git-fsck(1) Manual Page <h2>SYNOPSIS</h2>
<div class="sectionbody">
<div class="verseblock">
-<div class="content"><em>git-fsck</em> [--tags] [--root] [--unreachable] [--cache] [--no-reflogs]
+<div class="content"><em>git fsck</em> [--tags] [--root] [--unreachable] [--cache] [--no-reflogs]
[--full] [--strict] [--verbose] [--lost-found] [<object>*]</div></div>
</div>
<h2>DESCRIPTION</h2>
@@ -290,7 +290,7 @@ git-fsck(1) Manual Page <p>
An object to treat as the head of an unreachability trace.
</p>
-<p>If no objects are given, git-fsck defaults to using the
+<p>If no objects are given, <tt>git-fsck</tt> defaults to using the
index file, all SHA1 references in .git/refs/*, and all reflogs (unless
--no-reflogs is given) as heads.</p>
</dd>
@@ -394,14 +394,14 @@ that aren't readable from any of the specified head nodes.</p> <p>So for example</p>
<div class="literalblock">
<div class="content">
-<pre><tt>git-fsck --unreachable HEAD $(cat .git/refs/heads/*)</tt></pre>
+<pre><tt>git fsck --unreachable HEAD $(cat .git/refs/heads/*)</tt></pre>
</div></div>
<p>will do quite a _lot_ 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 "git-fsck" is happy, you
+sorted properly etc), but on the whole if <tt>git-fsck</tt> is happy, you
do have a valid tree.</p>
<p>Any corrupt objects you will have to find in backups or other archives
-(i.e., you can just remove them and do an "rsync" with some other site in
+(i.e., you can just remove them and do an <tt>rsync</tt> with some other site in
the hopes that somebody else has the object you have corrupted).</p>
<p>Of course, "valid tree" doesn't mean that it wasn't generated by some
evil person, and the end result might be crap. git is a revision
@@ -522,7 +522,7 @@ GIT_ALTERNATE_OBJECT_DIRECTORIES </div>
<div id="footer">
<div id="footer-text">
-Last updated 08-Jun-2008 01:33:43 UTC
+Last updated 02-Jul-2008 03:01:46 UTC
</div>
</div>
</body>
|