From: Eric Blake <eblake@redhat.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: gnulib-tool: Stop doing license notice replacements
Date: Fri, 4 Jun 2021 15:49:38 -0500 [thread overview]
Message-ID: <20210604204938.53p5ylm6rfmljzs7@redhat.com> (raw)
In-Reply-To: <5904386.tggPbNLTug@omega>
On Fri, Jun 04, 2021 at 10:29:22PM +0200, Bruno Haible wrote:
> As agreed upon in the thread starting at
> <https://lists.gnu.org/archive/html/bug-gnulib/2021-05/msg00102.html>.
>
>
> +++ b/doc/gnulib-intro.texi
> @@ -455,15 +455,22 @@ proofreading the patch.
> @section Copyright
>
> Most modules are under the GPL@. Some, mostly modules which can
> -reasonably be used in libraries, are under LGPL@. The source files
> -always say "GPL", but the real license specification is in the module
> -description file. If the module description file says "GPL", it means
> -"GPLv3+" (GPLv3 or newer, at the licensee's choice); if it says "LGPL",
> -it means "LGPLv3+" (LGPLv3 or newer, at the licensee's choice).
> +reasonably be used in libraries, are under LGPL@. Few modules are
> +under other licenses, such as LGPLv2+, unlimited, or public domain.
Would read better as "A few modules are..."
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2021-06-04 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 20:29 gnulib-tool: Stop doing license notice replacements Bruno Haible
2021-06-04 20:49 ` Eric Blake [this message]
2021-06-04 21:11 ` 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=20210604204938.53p5ylm6rfmljzs7@redhat.com \
--to=eblake@redhat.com \
--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).