summaryrefslogtreecommitdiffstats
path: root/git-fsck-objects.html
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2006-06-04 07:24:48 +0000
committerJunio C Hamano <junio@hera.kernel.org>2006-06-04 07:24:48 +0000
commit341071d878757c06a3931db660fe318effc8317e (patch)
tree8cb7bf28351c062adbe71172b942a3228d40725d /git-fsck-objects.html
parentbb8fb05ed082c81af81f9eecf356f993e2ef83b7 (diff)
downloadgit-htmldocs-341071d878757c06a3931db660fe318effc8317e.tar.gz
Autogenerated HTML docs for v1.3.3-g16a4
Diffstat (limited to 'git-fsck-objects.html')
-rw-r--r--git-fsck-objects.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/git-fsck-objects.html b/git-fsck-objects.html
index a325c927e..6fb08a168 100644
--- a/git-fsck-objects.html
+++ b/git-fsck-objects.html
@@ -370,7 +370,7 @@ extra validity tests to be added (make sure that tree objects are
sorted properly etc), but on the whole if "git-fsck-objects" is happy, you
do have a valid tree.</p>
<p>Any corrupt objects you will have to find in backups or other archives
-(ie you can just remove them and do an "rsync" with some other site in
+(i.e., you can just remove them and do an "rsync" 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
@@ -491,7 +491,7 @@ GIT_ALTERNATE_OBJECT_DIRECTORIES
</div>
<div id="footer">
<div id="footer-text">
-Last updated 13-Mar-2006 08:20:13 UTC
+Last updated 04-Jun-2006 07:24:27 UTC
</div>
</div>
</body>