From: Martin Ågren Date: Wed, 6 Mar 2019 06:30:15 +0000 (+0100) Subject: config/fsck.txt: avoid starting line with dash X-Git-Tag: v2.22.0-rc0~116^2~3 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=bc42e1e767fa86261fb5fdc5a495ad3ee14a9e0b;p=thirdparty%2Fgit.git config/fsck.txt: avoid starting line with dash This dash at the start of the line causes Asciidoctor to trip on the list continuations that follow and to render the pluses literally. Rewrap a little to put the dash elsewhere. Signed-off-by: Martin Ågren Signed-off-by: Junio C Hamano --- diff --git a/Documentation/config/fsck.txt b/Documentation/config/fsck.txt index 879c5a29c4..450e8c38e3 100644 --- a/Documentation/config/fsck.txt +++ b/Documentation/config/fsck.txt @@ -23,9 +23,9 @@ When `fsck.` is set, errors can be switched to warnings and vice versa by configuring the `fsck.` setting where the `` is the fsck message ID and the value is one of `error`, `warn` or `ignore`. For convenience, fsck prefixes the error/warning -with the message ID, e.g. "missingEmail: invalid author/committer line -- missing email" means that setting `fsck.missingEmail = ignore` will -hide that issue. +with the message ID, e.g. "missingEmail: invalid author/committer +line - missing email" means that setting `fsck.missingEmail = ignore` +will hide that issue. + In general, it is better to enumerate existing objects with problems with `fsck.skipList`, instead of listing the kind of breakages these