From: Bruno Haible <bruno@clisp.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org
Subject: Re: two ill effects of maint.mk
Date: Thu, 10 Jun 2021 19:34:38 +0200 [thread overview]
Message-ID: <6470670.kW3Cupxru1@omega> (raw)
In-Reply-To: <1ac72169-92b8-a873-d122-3331f8c13552@cs.ucla.edu>
Paul Eggert wrote:
> How about this idea instead? Have the GNUmakefile code run the 'locale'
> command and include its output in the 'make' output. That way, the
> 'make' transcript would indicate this particular detail of the test
> environment.
It would make sense to have this info in the generated test-suite.log,
because people who report test failures frequently send this file
as part of their bug report.
Other than that, e.g. for "make [all]" and "make install", this added
info is useless.
So, I think your suggestion should be implemented in Automake's
test suite drivers, not in maint.mk.
Bruno
next prev parent reply other threads:[~2021-06-10 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 15:41 two ill effects of maint.mk Bruno Haible
2021-06-10 16:09 ` Paul Eggert
2021-06-10 17:12 ` Bruno Haible
2021-06-10 17:14 ` Bruno Haible
2021-06-10 17:21 ` Paul Eggert
2021-06-10 17:34 ` Bruno Haible [this message]
2021-06-10 17:38 ` Paul Eggert
2021-06-20 22:15 ` Bruno Haible
2021-06-21 2:47 ` Paul Eggert
2021-06-21 8:52 ` 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=6470670.kW3Cupxru1@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).