From: Joseph Myers <joseph@codesourcery.com>
To: Thorsten Kukuk <kukuk@suse.de>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH] deprecate libnsl (Version 3)
Date: Sat, 29 Oct 2016 18:19:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1610291806410.11193@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20161029103834.GA1348@suse.de>
On Sat, 29 Oct 2016, Thorsten Kukuk wrote:
> Hi,
>
> since I still got no feedback about the deprecation patches
> for sunrpc and libnsl and no try was made to get it into
> the last glibc version, I assume nobody is interested in
> really deprecating this old IPv4 only code to make it easier
> for other projects and users to switch to IPv6?
Could you give the URL for the latest patch versions, and for any relevant
discussions that might indicate consensus, lack thereof or other relevant
issues, when pinging a patch (and pings should be approximately weekly,
including the URL every time, with patches updated if they no longer apply
cleanly to current sources)? Please make sure the latest version is
self-contained with a full write-up explaining it so that there's no need
to refer back to previous versions / other emails for an understanding of
the change being made and the rationale for the change and the design used
(and that it includes NEWS entries pointing to any relevant replacement
libraries for users, etc.).
I suspect there's a lack of people familiar with the code and ready to
judge desirability of the change, which makes it especially important to
have a thorough self-contained explanation of everything included with the
patch (the NEWS entries of course should have such information aimed at
people building/using glibc so it's immediately obvious where they should
go to get libnsl, libnss* etc. and what changes to their code they might
need to use such replacements).
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2016-10-29 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 9:48 Thorsten Kukuk
2016-04-06 17:30 ` Joseph Myers
2016-04-08 13:11 ` Thorsten Kukuk
2016-06-23 6:46 ` Thorsten Kukuk
2016-10-29 10:38 ` Thorsten Kukuk
2016-10-29 18:19 ` Joseph Myers [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=alpine.DEB.2.20.1610291806410.11193@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=kukuk@suse.de \
--cc=libc-alpha@sourceware.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).