From fb6a3d862137c3f77c387729395a0c558950437b Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Wed, 27 Jul 2005 18:55:18 -0700 Subject: [PATCH] Document --strict flag to the fsck-cache command. Signed-off-by: Junio C Hamano --- Documentation/git-fsck-cache.txt | 10 +++++++++- fsck-cache.c | 2 +- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/Documentation/git-fsck-cache.txt b/Documentation/git-fsck-cache.txt index f1c18c10d..aaec2de03 100644 --- a/Documentation/git-fsck-cache.txt +++ b/Documentation/git-fsck-cache.txt @@ -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] [*] +'git-fsck-cache' [--tags] [--root] [--unreachable] [--cache] [--standalone | --full] [--strict] [*] DESCRIPTION ----------- @@ -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 diff --git a/fsck-cache.c b/fsck-cache.c index 6115514d4..e40c64332 100644 --- a/fsck-cache.c +++ b/fsck-cache.c @@ -445,7 +445,7 @@ int main(int argc, char **argv) continue; } if (*arg == '-') - usage("git-fsck-cache [--tags] [[--unreachable] [--cache] [--standalone | --full] *]"); + usage("git-fsck-cache [--tags] [--root] [[--unreachable] [--cache] [--standalone | --full] [--strict] *]"); } if (standalone && check_full) -- 2.30.2