public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: [PATCH] strerror.3: VERSIONS: Document that strerrorname_np() and strerrordesc_np() functions first appeared on glibc 2.32
Date: Wed, 17 Feb 2021 11:05:22 +0100	[thread overview]
Message-ID: <5bb47a4f-ca2a-2a65-3d40-2b69d4caab7c@gmail.com> (raw)
In-Reply-To: <20210217095231.27727-1-alx.manpages@gmail.com>

On 2/17/21 10:52 AM, Alejandro Colomar wrote:
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
> ---
> 
> Hi Michael,
> 
> I struggled to use strerrorname_np(), until I found that these were
> so new that Debian Sid didn't have them :)
> 
> Cheers,
> 
> Alex
> 
> ---
>   man3/strerror.3 | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/man3/strerror.3 b/man3/strerror.3
> index 5dfe76f69..07684c40a 100644
> --- a/man3/strerror.3
> +++ b/man3/strerror.3
> @@ -235,6 +235,11 @@ Insufficient storage was supplied to contain the error description string.
>   The
>   .BR strerror_l ()
>   function first appeared in glibc 2.6.
> +The
> +.BR strerrorname_np (),

tfix: please remove that comma :)

> +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).
> 


-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-02-17 10:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17  9:52 Alejandro Colomar
2021-02-17 10:05 ` Alejandro Colomar (man-pages) [this message]
2021-02-17 12:23 ` [PATCH v2] " Alejandro Colomar
2021-02-18  7:57   ` Michael Kerrisk (man-pages)

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=5bb47a4f-ca2a-2a65-3d40-2b69d4caab7c@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).