From: Paul Eggert <eggert@cs.ucla.edu>
To: Zack Weinberg <zackw@panix.com>, autoconf@gnu.org
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
Date: Thu, 01 Sep 2016 03:24:00 -0000 [thread overview]
Message-ID: <c29dd41d-69d5-cf56-582e-fb6ae20ed564@cs.ucla.edu> (raw)
In-Reply-To: <CAKCAbMgx-N-w4iuCh3+GkMOup=FQ749vd_qPJ2qyZusaVsnEgQ@mail.gmail.com>
Zack Weinberg wrote:
> Have I missed either a way to carry out the ideal solution, or a third
> alternative?
How about changing AC_HEADER_MAJOR to detect those warning messages?
next prev parent reply other threads:[~2016-09-01 3:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 2:27 Zack Weinberg
2016-09-01 3:24 ` Paul Eggert [this message]
2016-09-02 1:09 ` Zack Weinberg
2016-09-13 21:37 ` Eric Blake
2016-09-13 22:31 ` Eric Blake
2016-09-13 22:38 ` Eric Blake
2016-09-14 1:38 ` Zack Weinberg
2016-09-01 4:37 ` Nick Bowler
2016-09-01 5:51 ` Florian Weimer
2016-09-02 1:16 ` Zack Weinberg
2016-09-02 1:32 ` Paul Eggert
2016-09-02 1:58 ` Zack Weinberg
2016-09-13 21:51 ` Eric Blake
2016-09-01 8:35 ` Florian Weimer
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=c29dd41d-69d5-cf56-582e-fb6ae20ed564@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=autoconf@gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=zackw@panix.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).