From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
John Snow <jsnow@redhat.com>, 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, 7 Feb 2022 18:05:27 +0000 [thread overview]
Message-ID: <YgFfZ+2cy/g9RTLQ@redhat.com> (raw)
In-Reply-To: <87czjyhaza.fsf@linaro.org>
On Mon, Feb 07, 2022 at 04:54:25PM +0000, Alex Bennée wrote:
>
> 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.
I think it definitely ought to have the word 'python' in the
repo name, because there's talk of having bindings for other
languages and we want a reliable way to distinguish what repo
and project we're dealing with, if the remaining part of the
name is not very distinctive. 'python-qemu.qmp.git' seems
reasonable enough.
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-02-07 18:09 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
2022-02-07 17:48 ` John Snow
2022-02-07 18:05 ` Daniel P. Berrangé [this message]
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=YgFfZ+2cy/g9RTLQ@redhat.com \
--to=berrange@redhat.com \
--cc=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 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).