From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: configure messages: check for features, not for bugs
Date: Sun, 26 Jul 2020 11:05:59 -0700 [thread overview]
Message-ID: <3b36de33-d55e-fb1e-571d-fe62b6e3659c@cs.ucla.edu> (raw)
In-Reply-To: <3182581.7oEx4UWm9q@omega>
On 7/26/20 8:02 AM, Bruno Haible wrote:
> Does anyone see a problem with this? Here is a proposed set of patches.
I like this change, and don't see a problem with it. Thanks for doing that.
next prev parent reply other threads:[~2020-07-26 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 15:02 configure messages: check for features, not for bugs Bruno Haible
2020-07-26 18:05 ` Paul Eggert [this message]
2020-08-26 23:32 ` Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3b36de33-d55e-fb1e-571d-fe62b6e3659c@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.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).