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


[-- Attachment #1.1: Type: text/plain, Size: 3029 bytes --]

Hi Andrew,

On 11/11/22 00:31, Andrew Clayton wrote:
> While looking at which systems provide memmem(3) I have been able to
> discern the following:
> 
>    musl libc since v0.9.7 (2012)
>    bionic since Android 9 (2018)
> 
>    FreeBSD since 6.0 (2005)
>    OpenBSD since 5.4 (2013)
>    NetBSD
>    macOS
>    Illumos
> 
> For macOS and Illumos I checked the memmem(3) man page on those systems.
> For the rest there are links below to on-line man pages or commit logs.
> 
> Where I could determine what version memmem(3) was introduced, I've
> noted that in the man page.
> 
> Link: <http://git.musl-libc.org/cgit/musl/commit/src/string/memmem.c?id=c86f2974e2acd330be2d587173dd4dd56db82e22>
> Link: <https://android.googlesource.com/platform/bionic/+/android-9.0.0_r3/libc/bionic/memmem.cpp>
> Link: <https://www.freebsd.org/cgi/man.cgi?query=memmem&sektion=3&format=html>
> Link: <https://man.openbsd.org/memmem.3>
> Link: <https://anonhg.netbsd.org/src/diff/96a37d536271/common/lib/libc/string/memmem.c>
> Suggested-by: Alejandro Colomar <alx@kernel.org>
> Signed-off-by: Andrew Clayton <andrew@digital-domain.net>
> ---
> 
>   v2:
>    - Remove references to bionic and macOS from the man page
>    - Convert & to and
>    - Use Oxford comma
>    - Add dates where known to the commit message
>    - Use present tense for the subject line

Oh, thanks for this one!  I hadn't realized.  :P

> 
>   man3/memmem.3 | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/man3/memmem.3 b/man3/memmem.3
> index 134dffab0..cb0d3e195 100644
> --- a/man3/memmem.3
> +++ b/man3/memmem.3
> @@ -58,7 +58,9 @@ T}	Thread safety	MT-Safe
>   .sp 1
>   .SH STANDARDS
>   This function is not specified in POSIX.1,
> -but is present on a number of other systems.
> +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.

<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=6ff6f43d68164f99a8c3fb66f4525d145571310c>

Cheers,

Alex

>   .SH BUGS
>   .\" This function was broken in Linux libraries up to and including libc 5.0.9;
>   .\" there the

-- 
<http://www.alejandro-colomar.es/>

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

  reply	other threads:[~2022-11-11  0:00 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 [this message]
2022-11-11  0:04     ` Andrew Clayton
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=7c72c8b0-ddb1-ec66-3886-57f2f7ac192f@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=alx@kernel.org \
    --cc=andrew@digital-domain.net \
    --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