public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Roland McGrath <roland@hack.frob.com>
Cc: Andreas Schwab <schwab@suse.de>,
	"Carlos O'Donell" <carlos@redhat.com>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH v2] Remove union wait
Date: Tue, 12 Apr 2016 11:38:00 -0000	[thread overview]
Message-ID: <570CDE15.2020605@redhat.com> (raw)
In-Reply-To: <20160411215550.692942C3AC8@topped-with-meat.com>

On 04/11/2016 11:55 PM, Roland McGrath wrote:

> But I will point out that the claim that the deprecation warnings are
> just as bad as outright removal is not really right.  Packagers or
> system-builders or whoever can add -Wno-error=deprecated to the
> compilation flags for a particular package via configure, or for an
> entire package-building system in that system's configuration for
> building all packages (a la redhat-rpm-config), etc.

There are so many build systems out there.  Figuring out how to disable 
-Werror is often more complicated than patching sources to get rid of 
the warning (especially if there are few places where the warning 
triggers, and the required change is straightforward).  Some projects do 
this deliberately to prevent warnings from accumulating.

At scale (for an entire distribution which has just rebased glibc), 
there is sometimes little difference between the two approaches to get 
rid of the deprecation warning.

Florian

  reply	other threads:[~2016-04-12 11:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 16:26 Deprecate union wait and remove support from wait functions [BZ #19613] Florian Weimer
2016-03-07 20:38 ` Florian Weimer
2016-03-07 22:44   ` Paul Eggert
2016-03-07 22:55 ` Roland McGrath
2016-03-08  9:57   ` [PATCH v2] Remove union wait (was: Re: Deprecate union wait and remove support from wait functions [BZ #19613]) Florian Weimer
2016-03-30 11:47     ` [PATCH v2] Remove union wait Florian Weimer
2016-03-30 22:32       ` Roland McGrath
2016-03-30 23:00         ` Carlos O'Donell
2016-03-31  7:14           ` Andreas Schwab
2016-03-31 12:26             ` Florian Weimer
2016-03-31 12:32               ` Andreas Schwab
2016-04-04  9:05               ` Andreas Schwab
2016-04-08 12:56             ` Florian Weimer
2016-04-11  9:07               ` Andreas Schwab
2016-04-11 15:32                 ` Florian Weimer
2016-04-11 21:55                   ` Roland McGrath
2016-04-12 11:38                     ` Florian Weimer [this message]
2016-04-12 18:01                       ` Roland McGrath
2016-04-12 19:20                         ` Florian Weimer
2016-04-13 19:05                           ` Carlos O'Donell
2016-04-13 19:11                             ` Roland McGrath
2016-04-13 19:10                     ` Carlos O'Donell
2016-04-01 21:29           ` Roland McGrath
2016-04-02  1:18             ` Carlos O'Donell
2016-03-30 22:47     ` [PATCH v2] Remove union wait (was: Re: Deprecate union wait and remove support from wait functions [BZ #19613]) Roland McGrath
2016-04-01 21:42       ` [PATCH v2] Remove union wait Florian Weimer
2016-04-01 22:00         ` Roland McGrath

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=570CDE15.2020605@redhat.com \
    --to=fweimer@redhat.com \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=roland@hack.frob.com \
    --cc=schwab@suse.de \
    /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).