From: "Daniel P. Berrangé" <berrange@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Cleber Rosa <crosa@redhat.com>,
qemu-devel@nongnu.org, Kashyap Chamarthy <kchamart@redhat.com>,
Beraldo Leal <bleal@redhat.com>
Subject: Re: [qemu.qmp PATCH 09/12] add LGPLv2+ and GPLv2 LICENSE files
Date: Mon, 25 Apr 2022 12:00:31 +0100 [thread overview]
Message-ID: <YmZ/T2UHeRTJuRmX@redhat.com> (raw)
In-Reply-To: <20220422184940.1763958-10-jsnow@redhat.com>
On Fri, Apr 22, 2022 at 02:49:37PM -0400, John Snow wrote:
> This clarifies that the majority of this package is LGPLv2+. Copyright
> blurbs that pointed to QEMU's "COPYING" file are amended to point to
> this repository's "LICENSE" file instead.
>
> The only file that is not already licensed as LGPLv2+ is legacy.py,
> which is GPLv2 only. Amend the copyright blurb there to point to
> LICENSE_GPL2, which is a copy of qemu.git's COPYING file.
>
> legacy.py is scheduled for removal, at which point the license of this
> library will become exclusively LGPLv2+. As the package currently
> contains a mixture of LGPLv2+ and GPLv2 code, the trove classifiers will
> reflect this mixture until such time as the remaining GPLv2 code is
> removed.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
> FILES.rst | 3 +
> LICENSE | 481 ++++++++++++++++++++++++++++++++++++++++++
> LICENSE_GPL2 | 339 +++++++++++++++++++++++++++++
> qemu/qmp/__init__.py | 2 +-
> qemu/qmp/legacy.py | 2 +-
> qemu/qmp/qmp_shell.py | 2 +-
> qemu/qmp/qmp_tui.py | 2 +-
> setup.cfg | 1 +
> 8 files changed, 828 insertions(+), 4 deletions(-)
> create mode 100644 LICENSE
> create mode 100644 LICENSE_GPL2
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2022-04-25 11:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 18:49 [qemu.qmp PATCH 00/12] python: fork qemu.qmp python lib into independent repo John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 01/12] fork qemu.qmp from qemu.git John Snow
2022-04-25 10:37 ` Daniel P. Berrangé
2022-04-25 18:54 ` John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 02/12] update maintainer metadata John Snow
2022-04-25 10:54 ` Daniel P. Berrangé
2022-04-25 18:15 ` John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 03/12] update project description John Snow
2022-04-29 13:44 ` Beraldo Leal
2022-04-22 18:49 ` [qemu.qmp PATCH 04/12] update project URLs John Snow
2022-04-25 10:56 ` Daniel P. Berrangé
2022-04-25 18:19 ` John Snow
2022-04-26 7:55 ` Daniel P. Berrangé
2022-04-26 8:16 ` Kashyap Chamarthy
2022-04-26 16:38 ` John Snow
2022-04-29 14:06 ` Beraldo Leal
2022-04-29 15:48 ` John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 05/12] add a couple new trove classifiers John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 06/12] move README.rst to FILES.rst and update John Snow
2022-04-25 13:23 ` Kashyap Chamarthy
2022-04-22 18:49 ` [qemu.qmp PATCH 07/12] move PACKAGE.rst to README.rst " John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 08/12] docs: add versioning policy to README John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 09/12] add LGPLv2+ and GPLv2 LICENSE files John Snow
2022-04-25 11:00 ` Daniel P. Berrangé [this message]
2022-04-22 18:49 ` [qemu.qmp PATCH 10/12] update Pipfile John Snow
2022-04-22 18:49 ` [qemu.qmp PATCH 11/12] remove sub-dependency pins from Pipfile John Snow
2022-04-25 13:19 ` Kashyap Chamarthy
2022-04-22 18:49 ` [qemu.qmp PATCH 12/12] update VERSION to 0.0.0a1 John Snow
2022-04-29 14:09 ` Beraldo Leal
2022-04-29 17:18 ` [qemu.qmp PATCH 00/12] python: fork qemu.qmp python lib into independent repo John Snow
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=YmZ/T2UHeRTJuRmX@redhat.com \
--to=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=kchamart@redhat.com \
--cc=qemu-devel@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).