From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18003 invoked by alias); 18 Aug 2017 22:12:28 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 17988 invoked by uid 89); 18 Aug 2017 22:12:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=H*c:HHHH X-HELO: relay1.mentorg.com Date: Fri, 18 Aug 2017 22:12:00 -0000 From: Joseph Myers To: Steve Ellcey CC: DJ Delorie , Subject: Re: [PATCH] Remove compat from DEFAULT_CONFIG lookup strings In-Reply-To: <1503092097.2986.55.camel@cavium.com> Message-ID: References: <1503089397.2986.43.camel@cavium.com> <1503092097.2986.55.camel@cavium.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="-1152306461-683702998-1503094337=:1807" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2017-08/txt/msg00917.txt.bz2 ---1152306461-683702998-1503094337=:1807 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Content-length: 1155 On Fri, 18 Aug 2017, Steve Ellcey wrote: > On Fri, 2017-08-18 at 21:12 +0000, Joseph Myers wrote: > > On Fri, 18 Aug 2017, Steve Ellcey wrote: > > > > > > > > I would think so.  I did a search and didn't find any more "compat" > > > lookups beyond what you found.  Not doing these changes didn't cause > > > any testsuite failures but it does seem like they should be changed.  I > > > updated them and reran the testsuite and got no regressions.  Here is > > > an updated patch. > > Does this affect any defaults visible to glibc users?  If it does, it  > > needs an entry in the "Deprecated and removed features, and other changes  > > affecting compatibility" section of NEWS. > > I think everything is already in the 2.26 Depreciated section.  This > was done when the original patch to remove libnss_compat was made. > These changes are just dealing with the fact that that patch was > incomplete. But the impression that NEWS entry gives is that you can use --enable-obsolete-nsl to get back the previous semantics. Does your patch change the semantics in the --enable-obsolete-nsl case? -- Joseph S. Myers joseph@codesourcery.com ---1152306461-683702998-1503094337=:1807--