From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Bruno Haible <bruno@clisp.org>
Cc: Simon Josefsson <simon@josefsson.org>, bug-gnulib@gnu.org
Subject: Re: test suite failure caused by check-copyright script
Date: Thu, 27 May 2021 14:14:54 -0400 [thread overview]
Message-ID: <87eedsjb6p.fsf@gmail.com> (raw)
In-Reply-To: <7839570.1tq08n3iVn@omega> (Bruno Haible's message of "Thu, 27 May 2021 19:54:58 +0200")
Hi Bruno,
Bruno Haible <bruno@clisp.org> writes:
>> Sounds good!
>>
>> /Simon
>
> Thanks for all your voices.
>
> I plan to start implementing this decision this week-end.
Yay! I'll be happy to test it again after then, and report any
remaining problem there may be with running the test suite, so feel free
to ping.
Maxim
prev parent reply other threads:[~2021-05-27 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 4:11 test suite failure caused by check-copyright script Maxim Cournoyer
2021-05-23 11:19 ` Bruno Haible
2021-05-24 1:51 ` Paul Eggert
2021-05-26 17:30 ` Eric Blake
2021-05-27 14:44 ` Jim Meyering
2021-05-27 15:14 ` Simon Josefsson via Gnulib discussion list
2021-05-27 17:54 ` Bruno Haible
2021-05-27 18:14 ` Maxim Cournoyer [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=87eedsjb6p.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=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).