From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: Daniel Berrange <berrange@redhat.com>,
John Snow <jsnow@redhat.com>, Beraldo Leal <bleal@redhat.com>,
Eric Blake <eblake@redhat.com>, Cleber Rosa <crosa@redhat.com>
Subject: [PATCH 0/4] Python: relicense async qmp as LGPLv2+
Date: Fri, 25 Mar 2022 16:04:34 -0400 [thread overview]
Message-ID: <20220325200438.2556381-1-jsnow@redhat.com> (raw)
Patch 2 explains most of the why.
The only dangling exception is legacy.py (patch 1), which I have plans
to replace "soon" :tm: (after I fork this code out of qemu.git.)
John Snow (4):
python/aqmp: add explicit GPLv2 license to legacy.py
python/aqmp: relicense as LGPLv2+
python/qmp-shell: relicense as LGPLv2+
python/aqmp-tui: relicense as LGPLv2+
python/qemu/aqmp/__init__.py | 6 +++---
python/qemu/aqmp/aqmp_tui.py | 2 +-
python/qemu/aqmp/legacy.py | 11 +++++++++++
python/qemu/aqmp/qmp_shell.py | 7 ++++---
4 files changed, 19 insertions(+), 7 deletions(-)
--
2.34.1
next reply other threads:[~2022-03-25 20:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 20:04 John Snow [this message]
2022-03-25 20:04 ` [PATCH 1/4] python/aqmp: add explicit GPLv2 license to legacy.py John Snow
2022-03-25 20:04 ` [PATCH 2/4] python/aqmp: relicense as LGPLv2+ John Snow
2022-03-25 20:04 ` [PATCH 3/4] python/qmp-shell: " John Snow
2022-03-27 8:45 ` Marc-André Lureau
2022-03-29 11:08 ` Fam Zheng
2022-03-29 16:09 ` John Snow
2022-03-29 16:43 ` Luiz Capitulino
2022-03-30 1:59 ` Eduardo Habkost
2022-03-30 15:06 ` Daniel P. Berrangé
2022-03-30 15:46 ` John Snow
2022-03-30 16:37 ` Cleber Rosa
2022-03-25 20:04 ` [PATCH 4/4] python/aqmp-tui: " John Snow
2022-03-26 15:27 ` Niteesh G. S.
2022-03-29 16:05 ` John Snow
2022-03-30 17:04 ` [PATCH 0/4] Python: relicense async qmp " 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=20220325200438.2556381-1-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=eblake@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).