public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
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: Fri, 18 Aug 2017 21:12:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1708182111260.1807@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1503089397.2986.43.camel@cavium.com>

[-- Attachment #1: Type: text/plain, Size: 594 bytes --]

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.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2017-08-18 21:12 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 [this message]
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
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.1708182111260.1807@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).