From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Chetan Pant" <chetan4windows@gmail.com>,
qemu-trivial@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
"Daniel P . Berrange" <berrange@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] Fixing LGPL version number
Date: Thu, 8 Oct 2020 09:57:20 +0200 [thread overview]
Message-ID: <ba4f81dd-8e5c-1d50-311c-fdc41f9cc504@redhat.com> (raw)
In-Reply-To: <df199cc8-c383-ed03-6244-7a204e92397b@redhat.com>
On 08/10/2020 09.54, Philippe Mathieu-Daudé wrote:
> Hi,
>
> On 10/8/20 8:05 AM, Chetan Pant wrote:
>> There is no "version 2" of the "Lesser" General Public License. It is
>> either "GPL version 2.0" or "LGPL version 2.1". This patch replaces all
>> occurrences of "LGPL version 2" with "LGPL version 2.1" in comment section.
>
> This looks like a good cleanup!
>
> Since you already listed all the files using this license,
> it can be a good opportunity to correct and use the full
> license text (which is miswritten in various places):
>
> ---
>
> Copyright (C) <year> <name of author>
>
> This library is free software; you can redistribute it and/or modify it
> under the terms of the GNU Lesser General Public License as published by
> the Free Software Foundation; either version 2.1 of the License, or (at
> your option) any later version.
>
> This library is distributed in the hope that it will be useful, but
> WITHOUT ANY WARRANTY; without even the implied warranty of
> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser
> General Public License for more details.
>
> You should have received a copy of the GNU Lesser General Public License
> along with this library; if not, write to the Free Software Foundation,
> Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Please don't use that version. If the FSF move to another office again, we
have to update the whole mess again.
> Or simpler, add the SPDX identifier tag:
>
> SPDX-License-Identifier: LGPL-2.1-or-later
SPDX tags would be cool, of course, but it could also be done in a separate
patch later.
Thomas
next prev parent reply other threads:[~2020-10-08 7:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 6:05 [PATCH] Fixing LGPL version number Chetan Pant
2020-10-08 6:13 ` no-reply
2020-10-08 7:54 ` Philippe Mathieu-Daudé
2020-10-08 7:57 ` Thomas Huth [this message]
2020-10-08 8:40 ` Chetan
2020-10-08 8:48 ` Thomas Huth
2020-10-08 10:22 ` Daniel P. Berrangé
2020-10-08 10:55 ` Chetan
2020-10-08 9:04 ` Thomas Huth
2020-10-08 9:22 ` Chetan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ba4f81dd-8e5c-1d50-311c-fdc41f9cc504@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=chetan4windows@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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 NNTP newsgroup(s).