From: Joseph Myers <joseph@codesourcery.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
Paul Eggert <eggert@cs.ucla.edu>,
Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
Alejandro Colomar <alx@kernel.org>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH] bind.2, mount_setattr.2, openat2.2, perf_event_open.2, pidfd_send_signal.2, recvmmsg.2, seccomp_unotify.2, select_tut.2, sendmmsg.2, set_thread_area.2, sysctl.2, bzero.3, getaddrinfo.3, getaddrinfo_a.3, getutent.3, mbrtowc.3, mbsinit.3, rti...
Date: Fri, 6 Jan 2023 17:01:13 +0000 [thread overview]
Message-ID: <b6f134c0-1e3a-4685-3669-b4093f3aa6@codesourcery.com> (raw)
In-Reply-To: <91de4293-9237-68d5-7743-9519f4259ecb@gmail.com>
On Fri, 6 Jan 2023, Alejandro Colomar via Libc-alpha wrote:
> P.S.: To compensate for the time I'm taking from you, I'm preparing a patch
> to remove rawmemchr(3) from glibc. I'll send it when it's "ready". Although
Don't waste your time. The criterion for removing a function is something
close to "never did anything meaningful or useful; no binary could ever
have successfully used the function with the ABI with which it was
defined"; otherwise we'd need a compelling case for how removing the
function can't break any existing binaries or sources we'd care about.
Even turning a function into a compat symbol, so making it unavailable to
new programs (while keeping it for existing binaries and keeping glibc
tests of that compat symbol), requires a much stronger deprecation basis
than "there are standard functions that are just as good". And marking
functions as deprecated with an attribute in headers - normally desirable
several releases before making a function into a compat symbol, at least -
also needs such a stronger deprecation basis; nothing in this thread
suggests any basis for marking *any* string functions as deprecated to me.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-01-06 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 15:53 Wilco Dijkstra
2023-01-06 16:20 ` Alejandro Colomar
2023-01-06 17:01 ` Joseph Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-06 2:26 Wilco Dijkstra
2023-01-06 13:49 ` Alejandro Colomar
2023-01-06 0:02 Wilco Dijkstra
2023-01-06 0:22 ` Alejandro Colomar
2023-01-06 0:57 ` Alejandro Colomar
2023-01-05 19:37 [PATCH] bind.2, mount_setattr.2, openat2.2, perf_event_open.2, pidfd_send_signal.2, recvmmsg.2, seccomp_unotify.2, select_tut.2, sendmmsg.2, set_thread_area.2, sysctl.2, bzero.3, getaddrinfo.3, getaddrinfo_a.3, getutent.3, mbrtowc.3, mbsinit.3, rtime.3, rtnetlink.3, strptime.3, NULL.3const, size_t.3type, void.3type, aio.7, netlink.7, unix.7: Prefer bzero(3) over memset(3) Alejandro Colomar
2023-01-05 20:48 ` Adhemerval Zanella Netto
2023-01-05 20:55 ` Paul Eggert
2023-01-05 21:12 ` [PATCH] bind.2, mount_setattr.2, openat2.2, perf_event_open.2, pidfd_send_signal.2, recvmmsg.2, seccomp_unotify.2, select_tut.2, sendmmsg.2, set_thread_area.2, sysctl.2, bzero.3, getaddrinfo.3, getaddrinfo_a.3, getutent.3, mbrtowc.3, mbsinit.3, rti Wilco Dijkstra
2023-01-05 21:33 ` Alejandro Colomar
2023-01-05 23:30 ` Wilco Dijkstra
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=b6f134c0-1e3a-4685-3669-b4093f3aa6@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=alx.manpages@gmail.com \
--cc=alx@kernel.org \
--cc=brauner@kernel.org \
--cc=eggert@cs.ucla.edu \
--cc=g.branden.robinson@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).