From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Greg Kurz" <groug@kaod.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [RFC] Move tools sources to the tools directory (was Re: [PATCH v2] MAINTAINERS: Fix the location of tools manuals)
Date: Thu, 4 Feb 2021 15:04:02 +0000 [thread overview]
Message-ID: <20210204150402.GP549438@redhat.com> (raw)
In-Reply-To: <CAFEAcA_=ANGKcy7QNfEdxUft9qGyCHttHo9hfvjQHC_ZfYeo1g@mail.gmail.com>
On Thu, Feb 04, 2021 at 02:50:08PM +0000, Peter Maydell wrote:
> On Thu, 4 Feb 2021 at 14:47, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > The distinction of contrib/ vs tools/ is supposed to be more a
> > reflection on the quality of the program.
> >
> > contrib/ should be considered demo-ware, no back compat guaranteed,
> > may or may not work, no testing guaranteed, no man pages.
>
> On this definition, why do we have any of it in our source tree?
> Interesting but unmaintained side things can live quite happily
> elsewhere (other peoples' git forks, blog posts, whatever).
Yes, broadly speaking I would actually agree with this. I think much of
this could easily live outside of qemu.git, beit a separate repo uner
QEMU project namespace, or a complete 3rd party.
Especially the vhost-user stuff has no dependency on QEMU in general
and could be used with other KVM userspaces.
> If we care about a bit of code enough to keep it in our source
> tree we ought to care about it enough to properly document
> and test it and give it a suitable place to live.
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:[~2021-02-04 15:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 13:54 [PATCH v2] MAINTAINERS: Fix the location of tools manuals Wainer dos Santos Moschetta
2021-02-04 13:59 ` Philippe Mathieu-Daudé
2021-02-04 14:22 ` [RFC] Move tools sources to the tools directory (was Re: [PATCH v2] MAINTAINERS: Fix the location of tools manuals) Wainer dos Santos Moschetta
2021-02-04 14:31 ` Peter Maydell
2021-02-04 14:40 ` Kevin Wolf
2021-02-04 14:47 ` Daniel P. Berrangé
2021-02-04 14:50 ` Peter Maydell
2021-02-04 15:02 ` Paolo Bonzini
2021-02-04 15:06 ` Daniel P. Berrangé
2021-02-04 17:37 ` Philippe Mathieu-Daudé
2021-02-04 17:39 ` Paolo Bonzini
2021-02-04 15:04 ` Daniel P. Berrangé [this message]
2021-02-04 14:57 ` Kevin Wolf
2021-02-04 14:47 ` Peter Maydell
2021-02-04 14:40 ` Paolo Bonzini
2021-02-04 17:42 ` Philippe Mathieu-Daudé
2021-02-04 17:55 ` Paolo Bonzini
2021-02-04 18:24 ` Eric Blake
2021-02-04 20:57 ` John Snow
2021-03-09 17:41 ` [PATCH v2] MAINTAINERS: Fix the location of tools manuals Wainer dos Santos Moschetta
2021-03-09 19:48 ` Thomas Huth
2021-03-09 20:44 ` Laurent Vivier
2021-03-09 22:54 ` Greg Kurz
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=20210204150402.GP549438@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=groug@kaod.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wainersm@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.