From: Peter Maydell <peter.maydell@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Konstantin Kostiuk" <kkostiuk@redhat.com>,
"Eric Blake" <eblake@redhat.com>
Subject: Re: Cleaning up contrib/ and tools/
Date: Wed, 25 Mar 2026 16:43:08 +0000 [thread overview]
Message-ID: <CAFEAcA_HLgphjGev_+HG_1KQChEZJKk3+9qP7_q79doG1EWD3Q@mail.gmail.com> (raw)
In-Reply-To: <f81e71f3-fe15-459a-9c27-2aea1592d155@linaro.org>
On Wed, 25 Mar 2026 at 15:17, Pierrick Bouvier
<pierrick.bouvier@linaro.org> wrote:
>
> On 3/25/26 4:11 AM, Alex Bennée wrote:
> > The aim have having these more complete plugins in the source tree was
> > to ensure they where updated as APIs change as well as provide useful
> > tools compared to the more toy like implementations we use for
> > check-tcg.
> >
> > I'm not sure about having them directly in the plugins folder as their
> > implementation is meant to be separated from the core QEMU code itself.
> > Maybe tools/plugins?
>
> Fine for me.
> Peter, is that ok for you too?
It doesn't really fit with "tools/ is where we put the things
which --enable-tools causes us to build and which we document
in docs/tools". The plugins are neither of those. That's why
I thought some subdirectory of plugins/ would fit better.
-- PMM
next prev parent reply other threads:[~2026-03-25 16:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 17:09 Cleaning up contrib/ and tools/ Peter Maydell
2026-03-24 17:31 ` Daniel P. Berrangé
2026-03-24 18:28 ` Pierrick Bouvier
2026-03-24 18:33 ` Peter Maydell
2026-03-24 18:44 ` Pierrick Bouvier
2026-03-25 9:21 ` Daniel P. Berrangé
2026-03-25 10:05 ` Marc-André Lureau
2026-03-25 11:11 ` Alex Bennée
2026-03-25 15:17 ` Pierrick Bouvier
2026-03-25 16:43 ` Peter Maydell [this message]
2026-03-25 7:42 ` Kostiantyn Kostiuk
2026-03-25 11:43 ` Markus Armbruster
2026-03-25 14:32 ` Alex Bennée
2026-03-25 16:49 ` Peter Maydell
2026-03-25 16:54 ` Daniel P. Berrangé
2026-03-25 19:41 ` Peter Maydell
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=CAFEAcA_HLgphjGev_+HG_1KQChEZJKk3+9qP7_q79doG1EWD3Q@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kkostiuk@redhat.com \
--cc=michael.roth@amd.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@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