From: Eric Blake <eblake@redhat.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: test suite failure caused by check-copyright script
Date: Wed, 26 May 2021 12:30:56 -0500 [thread overview]
Message-ID: <20210526173056.xh534pqyurijfhje@redhat.com> (raw)
In-Reply-To: <8449867.oamTS1uBFA@omega>
On Sun, May 23, 2021 at 01:19:23PM +0200, Bruno Haible wrote:
> Does everyone still agree
> - to put into the source files a license header that is consistent
> with the module description, and
> - to remove the statement from the documentation
> "The source files always say "GPL", but the real license
> specification is in the module description file." ?
Yes, that's fine with me.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2021-05-26 17:36 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 [this message]
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
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=20210526173056.xh534pqyurijfhje@redhat.com \
--to=eblake@redhat.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=maxim.cournoyer@gmail.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).