Re: [PATCH v3 02/16] docs: admin-guide: reporting-issues.rst: replace some characters
From: Thorsten Leemhuis <linux@leemhuis.info>
Date: 2021-05-16 10:28:43
Also in:
lkml
Lo! On one hand I think it would be good to fix the tools to make them understand non-breakable spaces in places where the author chose to use them, but whatever, their use in that sentence is definitely not important, so feel free to add: Acked-by: Thorsten Leemhuis <linux@leemhuis.info> Thanks for working on this. Ciao, Thorsten On 16.05.21 12:18, Mauro Carvalho Chehab wrote:
quoted hunk ↗ jump to hunk
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).