From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
libc-alpha@sourceware.org
Subject: Re: [PATCH v2] strerror.3: VERSIONS: Document that strerrorname_np() and strerrordesc_np() functions first appeared on glibc 2.32
Date: Thu, 18 Feb 2021 08:57:47 +0100 [thread overview]
Message-ID: <4af8b445-2d65-fbd2-7e15-eda8fd8bd0cc@gmail.com> (raw)
In-Reply-To: <20210217122310.107318-1-alx.manpages@gmail.com>
Hi Alex,
On 2/17/21 1:23 PM, Alejandro Colomar wrote:
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Thanks. Patch applied.
Cheers,
Michael
> ---
> man3/strerror.3 | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/man3/strerror.3 b/man3/strerror.3
> index 5dfe76f69..e1724a102 100644
> --- a/man3/strerror.3
> +++ b/man3/strerror.3
> @@ -235,6 +235,12 @@ Insufficient storage was supplied to contain the error description string.
> The
> .BR strerror_l ()
> function first appeared in glibc 2.6.
> +.PP
> +The
> +.BR strerrorname_np ()
> +and
> +.BR strerrordesc_np ()
> +functions first appeared in glibc 2.32.
> .SH ATTRIBUTES
> For an explanation of the terms used in this section, see
> .BR attributes (7).
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2021-02-18 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 9:52 [PATCH] strerror.3: VERSIONS: Document that strerrorname_np() and strerrordesc_np() functions first appeared on glibc 2.32 Alejandro Colomar
2021-02-17 10:05 ` Alejandro Colomar (man-pages)
2021-02-17 12:23 ` [PATCH v2] " Alejandro Colomar
2021-02-18 7:57 ` Michael Kerrisk (man-pages) [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=4af8b445-2d65-fbd2-7e15-eda8fd8bd0cc@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=libc-alpha@sourceware.org \
--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