[PATCH 2/5] config/fsck.txt: avoid starting line with dash
- From
- Martin Ågren <martin.agren@gmail.com>
- Date
- Mar 6, 2019, 06:30 UTC
- Message-ID
- <d3d025240b6a7a18323173cbaeeb8dab72429904.1551853194.git.martin.agren@gmail.com>
- In-Reply-To
- <cover.1551853194.git.martin.agren@gmail.com>
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 <martin.agren@gmail.com> --- Documentation/config/fsck.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
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.<msg-id>` is set, errors can be switched to warnings and vice versa by configuring the `fsck.<msg-id>` setting where the `<msg-id>` 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
-- 2.21.0