From: Alejandro Colomar <alx@kernel.org>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: linux-man@vger.kernel.org
Subject: Re: Two STANDARDS sections in strncpy(3)
Date: Mon, 6 Nov 2023 23:20:37 +0100 [thread overview]
Message-ID: <ZUlmtik0uAHkOhO7@debian> (raw)
In-Reply-To: <CACb0b4mpEWz6D-4SjYmLJsOfdYoSJ1Y2Bri+aFKcgKstXQt33g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
Hi Jonathan,
On Mon, Nov 06, 2023 at 09:02:20PM +0000, Jonathan Wakely wrote:
> The strncpy(3) page has two STANDARDS sections, which disagree. I
> think maybe the second one is supposed to be HISTORY.
>
> https://man7.org/linux/man-pages/man3/strncpy.3.html
Yup. Thanks!
Fixed:
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=ca77220a8fc5d25cf0f040f9ac9529a0cc12ed16>
Cheers,
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-11-06 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 21:02 Two STANDARDS sections in strncpy(3) Jonathan Wakely
2023-11-06 22:20 ` Alejandro Colomar [this message]
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=ZUlmtik0uAHkOhO7@debian \
--to=alx@kernel.org \
--cc=jwakely@redhat.com \
--cc=linux-man@vger.kernel.org \
/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