diff options
| author | John Cai <johncai86@gmail.com> | 2022-10-25 15:42:23 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2022-10-25 15:44:18 -0700 |
| commit | f6534dbda474ce9c4ce06c1f3212745724dd1724 (patch) | |
| tree | c5de190a23a24e013107b07bd6e4d0575e4de7ec /Documentation/config | |
| parent | 7edfb883abf46f514ca213efc4e04624d2ed540a (diff) | |
| download | git-f6534dbda474ce9c4ce06c1f3212745724dd1724.tar.gz | |
fsck: document msg-id
The documentation lacks mention of specific <msg-id> that are supported.
While git-help --config will display a list of these options, often
developers' first instinct is to consult the git docs to find valid
config values.
Add a list of fsck error messages, and link to it from the git-fsck
documentation.
Signed-off-by: John Cai <johncai86@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/config')
| -rw-r--r-- | Documentation/config/fsck.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/Documentation/config/fsck.txt b/Documentation/config/fsck.txt index 450e8c38e3..a3c865df56 100644 --- a/Documentation/config/fsck.txt +++ b/Documentation/config/fsck.txt @@ -35,6 +35,10 @@ allow new instances of the same breakages go unnoticed. Setting an unknown `fsck.<msg-id>` value will cause fsck to die, but doing the same for `receive.fsck.<msg-id>` and `fetch.fsck.<msg-id>` will only cause git to warn. ++ +See `Fsck Messages` section of linkgit:git-fsck[1] for supported +values of `<msg-id>`. + fsck.skipList:: The path to a list of object names (i.e. one unabbreviated SHA-1 per |