From: Bruno Haible <bruno@clisp.org>
To: Simon Josefsson <simon@josefsson.org>
Cc: bug-gnulib@gnu.org
Subject: Re: [PATCH] valgrind-tests: Better option handling.
Date: Fri, 14 May 2021 22:01:14 +0200 [thread overview]
Message-ID: <2233396.VZ1ULe7JWd@omega> (raw)
In-Reply-To: <87o8ddw6ze.fsf@latte.josefsson.org>
Hi Simon,
> > Assuming I am a GNU package maintainer and I read this paragraph. How do
> > I know whether my package uses the "old serial test harness"? Can I
> > determine this by looking at configure.ac? Or at the main Makefile.am?
>
> I suspect almost everyone is using the parallel test harness now since
> it is the default since automake 1.11.3, however I clarified the manual,
> does it look okay?
Yes, this is clear now. Everyone can now see which test harness their package
is using. Mine are indeed using the new (parallel) one :-)
Thanks.
Bruno
prev parent reply other threads:[~2021-05-14 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 12:27 [PATCH] valgrind-tests: Better option handling Simon Josefsson via Gnulib discussion list
2021-05-14 13:07 ` Simon Josefsson via Gnulib discussion list
2021-05-14 13:47 ` Bruno Haible
2021-05-14 17:38 ` Simon Josefsson via Gnulib discussion list
2021-05-14 20:01 ` Bruno Haible [this message]
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=2233396.VZ1ULe7JWd@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=simon@josefsson.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).