doc/fsck: clarify --connectivity-only behavior
On reading this again, there are two things that were not immediately clear to me: - we do still check links to blobs, even though we don't open the blobs themselves - we do not do the normal fsck checks, even for non-blob objects we do open Let's reword it to make these points a little more clear. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jeff King committed
Mar 4, 2019 at 23:46 UTC
df805ed6cfdc3345ce238101104c51bef5ec09e7
1 file changed
+7
-3
Documentation/git-fsck.txt
+7
-3
@@ -62,9 +62,13 @@ index file, all SHA-1 references in `refs` namespace, and all reflogs
62
with --no-full.
63
64
--connectivity-only::
65
- Check only the connectivity of tags, commits and tree objects. By
66
- avoiding to unpack blobs, this speeds up the operation, at the
67
- expense of missing corrupt objects or other problematic issues.
65
+ Check only the connectivity of reachable objects, making sure
66
+ that any objects referenced by a reachable tag, commit, or tree
67
+ is present. This speeds up the operation by avoiding reading
68
+ blobs entirely (though it does still check that referenced blobs
69
+ exist). This will detect corruption in commits and trees, but
70
+ not do any semantic checks (e.g., for format errors). Corruption
71
+ in blob objects will not be detected at all.
72
73
--strict::
74
Enable more strict checking, namely to catch a file mode