All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: John Snow <jsnow@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: Adding a 'qemu.qmp' repository to gitlab.com/qemu-project/
Date: Mon, 07 Feb 2022 16:54:25 +0000	[thread overview]
Message-ID: <87czjyhaza.fsf@linaro.org> (raw)
In-Reply-To: <CAFn=p-YxK8JduYOzxwDJSsmANgsqb+tK049t75VbXK-=Qi3J9w@mail.gmail.com>


John Snow <jsnow@redhat.com> writes:

> Hi Peter:
>
> I am working my way towards splitting the QMP library out of the
> qemu.git source tree. I'd like to ask for permission to:
>
> (1) Create a "qemu.qmp" repository under the qemu-project umbrella on
> GitLab

No objection for my part except maybe a better name? QemuPythonQmp? I
guess the header text can make it clear.

> (2) Add Cleber Rosa and myself as maintainers of this repository. (In
> discussion, Dan Berrange suggested a third maintainer for redundancy,
> but nobody from outside of RH has yet volunteered. The offer stands,
> but I have to press on in the meantime.)
>
> The initial patches that set up the new repository are not yet
> finalized and are still under review/development (on the qemu-devel
> list, as normal), but I wanted to reach out and directly ask if you
> have any objections to this plan so I can adjust the trajectory of my
> work if necessary.
>
> In short, the plan is to publish the QMP library as its own
> mini-project published to the Python package repository, and take
> patches via GitLab merge requests.
>
> Thanks,
> --js


-- 
Alex Bennée


  reply	other threads:[~2022-02-07 18:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 19:46 Adding a 'qemu.qmp' repository to gitlab.com/qemu-project/ John Snow
2022-02-07 16:54 ` Alex Bennée [this message]
2022-02-07 17:48   ` John Snow
2022-02-07 18:05   ` Daniel P. Berrangé
2022-02-08 18:54 ` Peter Maydell
2022-02-08 18:56   ` 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=87czjyhaza.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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 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.