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 <martin.agren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Martin Ågren 2019-03-06 07:30:15 +01:00 committed by Junio C Hamano
parent ef39d22fe6
commit bc42e1e767

View File

@ -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 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`, `<msg-id>` is the fsck message ID and the value is one of `error`,
`warn` or `ignore`. For convenience, fsck prefixes the error/warning `warn` or `ignore`. For convenience, fsck prefixes the error/warning
with the message ID, e.g. "missingEmail: invalid author/committer line with the message ID, e.g. "missingEmail: invalid author/committer
- missing email" means that setting `fsck.missingEmail = ignore` will line - missing email" means that setting `fsck.missingEmail = ignore`
hide that issue. will hide that issue.
+ +
In general, it is better to enumerate existing objects with problems In general, it is better to enumerate existing objects with problems
with `fsck.skipList`, instead of listing the kind of breakages these with `fsck.skipList`, instead of listing the kind of breakages these