From: Joseph Myers <joseph@codesourcery.com>
To: Steve Ellcey <sellcey@cavium.com>
Cc: DJ Delorie <dj@redhat.com>, <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Remove compat from DEFAULT_CONFIG lookup strings
Date: Mon, 28 Aug 2017 20:48:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1708282042270.13583@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1503951778.28672.139.camel@cavium.com>
On Mon, 28 Aug 2017, Steve Ellcey wrote:
> On Tue, 2017-08-22 at 17:07 -0400, DJ Delorie wrote:
> > I find the slight inconsistency in the use of [NOTFOUND=return] in
> > initgroups.c disconcerting, but IMHO that's irrelevent for this
> > particular change.
> >
> > LGTM.
>
> Joseph, do you have any issues with the latest version of this patch?
> I don't want to go ahead unless you think this has addressed the issues
> you had with the initial patch.
I think the documentation in the manual needs to be updated.
Specifically, nss.texi documents the defaults for various NSS databases,
and it needs to be made to reflect how the defaults depend on how glibc is
configured.
Does the "nis [NOTFOUND=return] files" default in
nsswitch.c:__nss_database_lookup need to change as well?
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-08-28 20:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 21:31 Steve Ellcey
2017-08-18 0:18 ` DJ Delorie
2017-08-18 20:50 ` Steve Ellcey
2017-08-18 21:12 ` Joseph Myers
2017-08-18 21:35 ` Steve Ellcey
2017-08-18 22:12 ` Joseph Myers
2017-08-18 22:17 ` Steve Ellcey
2017-08-22 16:33 ` Steve Ellcey
2017-08-22 21:07 ` DJ Delorie
2017-08-28 20:23 ` Steve Ellcey
2017-08-28 20:48 ` Joseph Myers [this message]
2017-08-28 21:50 ` Steve Ellcey
2017-08-28 22:58 ` Joseph Myers
2017-08-29 19:04 ` Steve Ellcey
2017-08-29 20:23 ` Joseph Myers
2017-08-29 20:57 ` DJ Delorie
2017-08-31 7:21 ` Andreas Schwab
2017-08-31 15:25 ` Steve Ellcey
2017-09-11 20:01 ` Steve Ellcey
2017-09-11 20:39 ` DJ Delorie
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.1708282042270.13583@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=sellcey@cavium.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).