From: John Snow <jsnow@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Damien Hedde <damien.hedde@greensocs.com>,
Peter Maydell <peter.maydell@linaro.org>,
Daniel Berrange <berrange@redhat.com>,
Victor Toso de Carvalho <victortoso@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Andrea Bolognani <abologna@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Cleber Rosa <crosa@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Create qemu-project/py-qemu.qmp repo
Date: Thu, 21 Apr 2022 12:46:48 -0400 [thread overview]
Message-ID: <CAFn=p-a1DTR3ve_aQBARLG6NDdGscWQOn1wCjrPiRWL0sDvk9A@mail.gmail.com> (raw)
Hi Alex: do you have the ability to create a blank/empty "py-qemu.qmp"
repo under the qemu-project grouping, and add me and Cleber as
maintainers for it? There weren't any objections when I floated the
idea [1].
(Though I suggested "py-qemu.qmp" and Dan suggested "python-qemu.qmp".
I don't think we explicitly reconciled the difference. I like the
shorter one.)
After my most recent Python PR is merged [2], I'll be just about ready
to go on pushing a fork of this library into its own repo [3], so I
think it's time to actually create the repo. I intend to re-spin that
fork patchset [3] (updating the URLs involved) and see if there are
any final comments, then push to the new repository.
[1] https://lists.gnu.org/archive/html/qemu-devel/2022-02/msg00979.html
[2] https://patchew.org/QEMU/20220421151600.984189-1-jsnow@redhat.com/
[3] https://lists.gnu.org/archive/html/qemu-devel/2022-03/msg07176.html
Thanks,
--js
next reply other threads:[~2022-04-21 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 16:46 John Snow [this message]
2022-04-21 17:59 ` Create qemu-project/py-qemu.qmp repo Andrea Bolognani
2022-04-21 21:00 ` John Snow
2022-04-22 8:37 ` Andrea Bolognani
2022-04-22 14:28 ` John Snow
2022-04-22 16:41 ` 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='CAFn=p-a1DTR3ve_aQBARLG6NDdGscWQOn1wCjrPiRWL0sDvk9A@mail.gmail.com' \
--to=jsnow@redhat.com \
--cc=abologna@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=damien.hedde@greensocs.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=victortoso@redhat.com \
/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).