public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Steve Ellcey <sellcey@cavium.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: DJ Delorie <dj@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] Remove compat from DEFAULT_CONFIG lookup strings
Date: Fri, 18 Aug 2017 22:17:00 -0000	[thread overview]
Message-ID: <1503094613.2986.59.camel@cavium.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1708182211180.1807@digraph.polyomino.org.uk>

On Fri, 2017-08-18 at 22:12 +0000, Joseph Myers wrote:
> 
> 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?

That is a good point.  I hadn't considered it, but this patch does
change the semantics when --enable-obsolete-nsl is used.  I  guess the
question is: do we think that is OK and just need to document the
changes or do we need to ifdef the code changes so that when --enable-
obsolete-nsl is used, we get the existing behavour.  I am inclined to 
ifdef the code to preserve the current behavour under the enable
option.

Steve Ellcey
sellcey@cavium.com

  reply	other threads:[~2017-08-18 22:17 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 [this message]
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
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=1503094613.2986.59.camel@cavium.com \
    --to=sellcey@cavium.com \
    --cc=dj@redhat.com \
    --cc=joseph@codesourcery.com \
    --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).