All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Kashyap Chamarthy <kchamart@redhat.com>,
	Daniel Berrange <berrange@redhat.com>,
	Beraldo Leal <bleal@redhat.com>, Cleber Rosa <crosa@redhat.com>
Subject: Re: [qemu.qmp PATCH 00/12] python: fork qemu.qmp python lib into independent repo
Date: Fri, 29 Apr 2022 13:18:36 -0400	[thread overview]
Message-ID: <CAFn=p-Yn+gBBWw0qpEngyuBv2_zNZFmO17b07EXps4k9=32jog@mail.gmail.com> (raw)
In-Reply-To: <20220422184940.1763958-1-jsnow@redhat.com>

On Fri, Apr 22, 2022 at 2:49 PM John Snow <jsnow@redhat.com> wrote:
>
> GitLab: https://gitlab.com/jsnow/qemu.qmp/-/commits/initial-checkin
>
> Hi, this series is part of an effort to publish the qemu.qmp package on
> PyPI. It is part of the second of three phases to complete this work:
>
>     (1) Switch the new Async QMP library in to python/qemu/qmp [merged!]
>     (2) Fork python/qemu/qmp out into its own repository.
> -->    (2a) Do the bare minimum to be consistent.
>        (2b) Add most GitLab CI/CD targets.
>        (2c) Add Sphinx doc builds, update docs, and publish to GitLab pages.
>        (2d) Add dynamic git versioning and GitLab package builds.
>     (3) Update qemu.git to install qemu.qmp from PyPI,
>         and then delete python/qemu/qmp.
>
> This series is not meant to apply to qemu.git, rather -- it's the series
> that performs the split and applies to the brand new repository.
>
> If there are no objections, I intend to push the content of this branch
> to https://gitlab.com/qemu-project/python-qemu-qmp within a week or so.
>
> Most URLs in this series have been updated to point to the new repo URL,
> except one link to https://jsnow.gitlab.io/qemu.qmp/ which will be
> updated when step (2c) above is handled.
>
> John Snow (12):
>   fork qemu.qmp from qemu.git
>   update maintainer metadata
>   update project description
>   update project URLs
>   add a couple new trove classifiers
>   move README.rst to FILES.rst and update
>   move PACKAGE.rst to README.rst and update
>   docs: add versioning policy to README
>   add LGPLv2+ and GPLv2 LICENSE files
>   update Pipfile
>   remove sub-dependency pins from Pipfile
>   update VERSION to 0.0.0a1
>
>  .gitignore            |   2 +-
>  FILES.rst             |  67 ++++++
>  LICENSE               | 481 ++++++++++++++++++++++++++++++++++++++++++
>  LICENSE_GPL2          | 339 +++++++++++++++++++++++++++++
>  MANIFEST.in           |   3 +-
>  Makefile              |  16 +-
>  PACKAGE.rst           |  43 ----
>  Pipfile               |   4 +-
>  Pipfile.lock          | 288 ++++++++++++++-----------
>  README.rst            | 272 ++++++++++++++++--------
>  VERSION               |   2 +-
>  qemu/qmp/__init__.py  |   2 +-
>  qemu/qmp/legacy.py    |   2 +-
>  qemu/qmp/qmp_shell.py |   2 +-
>  qemu/qmp/qmp_tui.py   |   2 +-
>  setup.cfg             |  41 ++--
>  setup.py              |   2 +-
>  17 files changed, 1262 insertions(+), 306 deletions(-)
>  create mode 100644 FILES.rst
>  create mode 100644 LICENSE
>  create mode 100644 LICENSE_GPL2
>  delete mode 100644 PACKAGE.rst
>
> --
> 2.34.1
>
>

Pushed directly as the initial commit.

https://gitlab.com/qemu-project/python-qemu-qmp

Thanks, everyone. I'll begin drafting and submitting merge requests
for further work on this repository and, for now, CCing the mailing
list pointing to the MRs.

--js



      parent reply	other threads:[~2022-04-29 17:20 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é
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 ` John Snow [this message]

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='CAFn=p-Yn+gBBWw0qpEngyuBv2_zNZFmO17b07EXps4k9=32jog@mail.gmail.com' \
    --to=jsnow@redhat.com \
    --cc=berrange@redhat.com \
    --cc=bleal@redhat.com \
    --cc=crosa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.