public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Clayton <andrew@digital-domain.net>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Alejandro Colomar <alx@kernel.org>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	linux-man@vger.kernel.org,
	Andrew Clayton <andrew@digital-domain.net>
Subject: Re: [PATCH v2] memmem.3: Add list of known systems where this is available
Date: Fri, 11 Nov 2022 00:04:40 +0000	[thread overview]
Message-ID: <20221111000440.0b4e08c9@kappa.digital-domain.net> (raw)
In-Reply-To: <7c72c8b0-ddb1-ec66-3886-57f2f7ac192f@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

On Fri, 11 Nov 2022 00:59:59 +0100
Alejandro Colomar <alx.manpages@gmail.com> wrote:

> > +but is present on a number of other systems,
> > +including: musl libc 0.9.7; FreeBSD 6.0, OpenBSD 5.4,
> > +NetBSD, and Illumos.  
> 
> I've been thinking about the line breaks.  I'm not sure how I'd split them, but 
> I'm not happy with the current suggestion.
> 
> Please see man-pages(7) about semantic newlines, and see if you come up with 
> something nicer.
> 
> man-pages(7):
>     Use semantic newlines
>         In  the  source of a manual page, new sentences should be
>         started on new lines, long sentences should be split into
>         lines at clause breaks (commas, semicolons,  colons,  and
>         so on), and long clauses should be split at phrase bound‐
>         aries.   This  convention,  sometimes  known as "semantic
>         newlines", makes it easier to see the effect of  patches,
>         which often operate at the level of individual sentences,
>         clauses, or phrases.

I guess the best thing then is to just break it on the semi-colon.

Andrew

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-11-11  0:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  0:13 [PATCH] memmem.3: Added list of known systems where this is available Andrew Clayton
2022-11-10 11:36 ` Alejandro Colomar
2022-11-10 12:58   ` Andrew Clayton
2022-11-10 14:16     ` Alejandro Colomar
2022-11-22 23:11   ` Guillem Jover
2022-11-23 12:52     ` Stefan Puiu
2022-11-23 13:16       ` Alejandro Colomar
2022-11-23 14:55         ` [musl] " Jeffrey Walton
2022-11-23 15:11           ` Alejandro Colomar
2022-11-24 18:57         ` Stefan Puiu
2022-12-11 16:30           ` Alejandro Colomar
2022-11-10 23:31 ` [PATCH v2] memmem.3: Add " Andrew Clayton
2022-11-10 23:59   ` Alejandro Colomar
2022-11-11  0:04     ` Andrew Clayton [this message]
2022-11-11  0:05       ` Alejandro Colomar
2022-11-11  0:20         ` Andrew Clayton
2022-11-11  0:21           ` Alejandro Colomar
2022-11-11  1:27 ` [PATCH v3] " Andrew Clayton
2022-11-11  1:35   ` Alejandro Colomar
2022-11-11 18:09   ` Brian Inglis

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=20221111000440.0b4e08c9@kappa.digital-domain.net \
    --to=andrew@digital-domain.net \
    --cc=alx.manpages@gmail.com \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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