From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
linux-man <linux-man@vger.kernel.org>,
Libc-alpha <libc-alpha@sourceware.org>,
"tech@openbsd.org" <tech@openbsd.org>,
"Klemens Nanni" <kn@openbsd.org>,
"Benoit Lecocq" <benoit@openbsd.org>,
git@vger.kernel.org
Subject: Re: Is getpass(3) really obsolete?
Date: Sat, 30 Oct 2021 14:24:55 +0200 [thread overview]
Message-ID: <fd78c241-c51e-03c6-1e6b-641536245fbd@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110291627330.1788146@digraph.polyomino.org.uk>
Hi Joseph,
On 10/29/21 18:31, Joseph Myers wrote:
> On Fri, 29 Oct 2021, Alejandro Colomar (man-pages) via Libc-alpha wrote:
>
>> The broader context is that I was trying to make the deprecation notices more
>> consistent in the Linux manpages, by using the [[deprecated]] attribute where
>> appropriate. While doing that, I found a few cases where the
>> deprecation/obsoletion is not so clear to me, such as this one
>> ([as]ctime[_r](3) is another one, since it is deprecated by POSIX, but not by
>> the C standard, but I'll start a different thread with that; and isascii(3) is
>
> See the discussion of deprecation starting with
> <https://sourceware.org/pipermail/libc-alpha/2021-May/126356.html> (C2X
> has also deprecated those functions). The comments in that thread
> supported marking the functions deprecated, but it needs someone to send a
> patch and I don't know what breakage might result in applications using
> those functions.
>
Thanks. The latest draft for C2x that I know of is N2596. Is there any
newer draft that I can consult for these things? I see many proposals,
but it's difficult to know which have been accepted and which not
without an actual recent draft of the standard.
Cheers,
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-10-30 12:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 11:15 Is getpass(3) really obsolete? Alejandro Colomar
2021-10-29 11:28 ` Alejandro Colomar (man-pages)
2021-10-29 11:40 ` Ævar Arnfjörð Bjarmason
2021-10-29 12:11 ` Alejandro Colomar (man-pages)
2021-10-29 16:31 ` Joseph Myers
2021-10-30 12:24 ` Alejandro Colomar (man-pages) [this message]
2021-11-01 21:31 ` Joseph Myers
2021-10-29 12:10 ` rsbecker
2021-10-29 13:55 ` Eugene Syromyatnikov
2021-10-29 13:55 ` Theo de Raadt
2021-10-29 14:18 ` rsbecker
2021-10-29 14:21 ` Theo de Raadt
2021-10-29 14:33 ` rsbecker
2021-10-29 14:44 ` Alejandro Colomar (man-pages)
2021-10-29 15:00 ` rsbecker
2021-10-29 14:53 ` Zack Weinberg
2022-09-27 19:19 ` readpassphrase(3) in glibc, and agetpass() (Was: Is getpass(3) really obsolete?) Alejandro Colomar
2022-09-27 19:33 ` Alex Colomar
2022-09-27 20:30 ` Sam James
2022-09-27 20:52 ` readpassphrase(3) in glibc, and agetpass() Junio C Hamano
2021-10-29 15:27 ` [PATCH] getpass.3: SYNOPSIS: Mark getpass() as [[deprecated]] Alejandro Colomar
2021-10-29 20:27 ` Is getpass(3) really obsolete? Jeff King
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=fd78c241-c51e-03c6-1e6b-641536245fbd@gmail.com \
--to=alx.manpages@gmail.com \
--cc=avarab@gmail.com \
--cc=benoit@openbsd.org \
--cc=git@vger.kernel.org \
--cc=joseph@codesourcery.com \
--cc=kn@openbsd.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=tech@openbsd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.