Hi Branden, On 8/8/21 10:41 AM, Alejandro Colomar wrote:
From: "G. Branden Robinson" <g.branden.robinson@xxxxxxxxx> Saw this while preparing the "switch to \~" change Alex invited.
Ping. You're still invited :-) Cheers, Alex
Signed-off-by: G. Branden Robinson <g.branden.robinson@xxxxxxxxx> Signed-off-by: Alejandro Colomar <alx.manpages@xxxxxxxxx> --- man7/man-pages.7 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man7/man-pages.7 b/man7/man-pages.7 index 6cb805343..3819dfd97 100644 --- a/man7/man-pages.7 +++ b/man7/man-pages.7 @@ -638,7 +638,7 @@ makes it easier to write tools that parse man page source files.) .SS Use semantic newlines In the source of a manual page, new sentences should be started on new lines, -and long sentences should split into lines at clause breaks +and long sentences should be split into lines at clause breaks (commas, semicolons, colons, and so on). This convention, sometimes known as "semantic newlines", makes it easier to see the effect of patches,
-- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/
