Browse Source

Document --strict flag to the fsck-cache command.

Signed-off-by: Junio C Hamano <junkio@cox.net>
maint
Junio C Hamano 20 years ago
parent
commit
fb6a3d8621
  1. 10
      Documentation/git-fsck-cache.txt
  2. 2
      fsck-cache.c

10
Documentation/git-fsck-cache.txt

@ -9,7 +9,7 @@ git-fsck-cache - Verifies the connectivity and validity of the objects in the da @@ -9,7 +9,7 @@ git-fsck-cache - Verifies the connectivity and validity of the objects in the da

SYNOPSIS
--------
'git-fsck-cache' [--tags] [--root] [--unreachable] [--cache] [--standalone | --full] [<object>*]
'git-fsck-cache' [--tags] [--root] [--unreachable] [--cache] [--standalone | --full] [--strict] [<object>*]

DESCRIPTION
-----------
@ -53,6 +53,14 @@ OPTIONS @@ -53,6 +53,14 @@ OPTIONS
and corresponding pack subdirectories in alternate
object pools; cannot be used with --standalone.

--strict::
Enable more strict checking, namely to catch a file mode
recorded with g+w bit set, which was created by older
versions of GIT. Existing repositories, including the
Linux kernel, GIT itself, and sparse repository have old
objects that triggers this check, but it is recommended
to check new projects with this flag.

It 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

2
fsck-cache.c

@ -445,7 +445,7 @@ int main(int argc, char **argv) @@ -445,7 +445,7 @@ int main(int argc, char **argv)
continue;
}
if (*arg == '-')
usage("git-fsck-cache [--tags] [[--unreachable] [--cache] [--standalone | --full] <head-sha1>*]");
usage("git-fsck-cache [--tags] [--root] [[--unreachable] [--cache] [--standalone | --full] [--strict] <head-sha1>*]");
}

if (standalone && check_full)

Loading…
Cancel
Save