git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Ågren" <martin.agren@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH 2/5] config/fsck.txt: avoid starting line with dash
Date: Wed,  6 Mar 2019 07:30:15 +0100	[thread overview]
Message-ID: <d3d025240b6a7a18323173cbaeeb8dab72429904.1551853194.git.martin.agren@gmail.com> (raw)
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


  parent reply	other threads:[~2019-03-06  6:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06  6:30 [PATCH 0/5] fixing a few Asciidoc/tor differences Martin Ågren
2019-03-06  6:30 ` [PATCH 1/5] config/diff.txt: drop spurious backtick Martin Ågren
2019-03-06  6:30 ` Martin Ågren [this message]
2019-03-06  6:30 ` [PATCH 3/5] git.txt: remove empty line before list continuation Martin Ågren
2019-03-06  6:30 ` [PATCH 4/5] git-svn.txt: drop escaping '\' that ends up being rendered Martin Ågren
2019-03-06  6:30 ` [PATCH 5/5] Documentation: turn middle-of-line tabs into spaces Martin Ågren
2019-03-07  0:29   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d3d025240b6a7a18323173cbaeeb8dab72429904.1551853194.git.martin.agren@gmail.com \
    --to=martin.agren@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).