All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Thorsten Leemhuis <linux@leemhuis.info>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 1/8] docs: admin-guide: reporting-issues.rst: replace some characters
Date: Wed, 16 Jun 2021 08:55:07 +0200	[thread overview]
Message-ID: <551a2af0e654226067e5c376d3e2d959cc738f39.1623826294.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1623826294.git.mchehab+huawei@kernel.org>

The conversion tools used during DocBook/LaTeX/html/Markdown->ReST
conversion and some cut-and-pasted text contain some characters that
aren't easily reachable on standard keyboards and/or could cause
troubles when parsed by the documentation build system.

Replace the occurences of the following characters:

	- U+00a0 (' '): NO-BREAK SPACE
	  as it can cause lines being truncated on PDF output

Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
 Documentation/admin-guide/reporting-issues.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/admin-guide/reporting-issues.rst b/Documentation/admin-guide/reporting-issues.rst
index 18d8e25ba9df..d7ac13f789cc 100644
--- a/Documentation/admin-guide/reporting-issues.rst
+++ b/Documentation/admin-guide/reporting-issues.rst
@@ -1248,7 +1248,7 @@ paragraph makes the severeness obvious.
 
 In case you performed a successful bisection, use the title of the change that
 introduced the regression as the second part of your subject. Make the report
-also mention the commit id of the culprit. In case of an unsuccessful bisection,
+also mention the commit id of the culprit. In case of an unsuccessful bisection,
 make your report mention the latest tested version that's working fine (say 5.7)
 and the oldest where the issue occurs (say 5.8-rc1).
 
-- 
2.31.1


  reply	other threads:[~2021-06-16  6:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16  6:55 [PATCH 0/8] Replace some bad characters on documents Mauro Carvalho Chehab
2021-06-16  6:55 ` [Intel-wired-lan] " Mauro Carvalho Chehab
2021-06-16  6:55 ` Mauro Carvalho Chehab
2021-06-16  6:55 ` Mauro Carvalho Chehab [this message]
2021-06-16  6:55 ` [PATCH 2/8] docs: trace: coresight: coresight-etm4x-reference.rst: replace some characters Mauro Carvalho Chehab
2021-06-16  6:55   ` Mauro Carvalho Chehab
2021-06-16  6:55 ` [PATCH 3/8] docs: driver-api: ioctl.rst: " Mauro Carvalho Chehab
2021-06-16  6:55 ` [PATCH 4/8] docs: usb: " Mauro Carvalho Chehab
2021-06-16  7:17   ` Greg Kroah-Hartman
2021-06-16  6:55 ` [PATCH 5/8] docs: vm: zswap.rst: " Mauro Carvalho Chehab
2021-06-16  6:55 ` [PATCH 6/8] docs: filesystems: ext4: blockgroup.rst: " Mauro Carvalho Chehab
2021-06-16 14:53   ` Theodore Ts'o
2021-06-16  6:55 ` [PATCH 7/8] docs: networking: device_drivers: " Mauro Carvalho Chehab
2021-06-16  6:55   ` [Intel-wired-lan] " Mauro Carvalho Chehab
2021-06-16  6:55 ` [PATCH 8/8] docs: PCI: Replace non-breaking spaces to avoid PDF issues Mauro Carvalho Chehab
2021-06-17 19:35 ` [PATCH 0/8] Replace some bad characters on documents Jonathan Corbet
2021-06-17 19:35   ` [Intel-wired-lan] " Jonathan Corbet
2021-06-17 19:35   ` Jonathan Corbet

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=551a2af0e654226067e5c376d3e2d959cc738f39.1623826294.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.