public inbox for qemu-devel@nongnu.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: "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>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
	"Eric Blake" <eblake@redhat.com>
Subject: Re: Cleaning up contrib/ and tools/
Date: Wed, 25 Mar 2026 19:41:53 +0000	[thread overview]
Message-ID: <CAFEAcA9fxumwc25utUqU23_Gj2SdpZDWSUYhhivejQjnQksEOA@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_DEPSoAnEzobryPbqU77QHwqYyxybmdi7KX2wjJqzRhw@mail.gmail.com>

On Wed, 25 Mar 2026 at 16:49, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Wed, 25 Mar 2026 at 11:44, Markus Armbruster <armbru@redhat.com> wrote:
> > Perhaps contrib/ is not a good home for example code.  It seems to
> > bother people whose judgement I respect.  Can we find a better home?
>
> I'm not sure to what extent we should be in the business of
> providing example code. If we are doing that we should label
> it all a bit better...

One thought that came to mind: for example code, perhaps we
should think of it in terms of it being part of our
documentation, so for instance:
 * shipping it (under /usr/share/qemu/code-examples/ ??
   as a subdir of the docs ???)
 * making sure the docs can hyperlink to the example code
 * making sure we have docs explaining the example code and
   what we intend to demonstrate by it (the plugins docs
   are very good here)

-- PMM


      parent reply	other threads:[~2026-03-25 19:42 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
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 [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=CAFEAcA9fxumwc25utUqU23_Gj2SdpZDWSUYhhivejQjnQksEOA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --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