From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: should we have a new 'tools' manual?
Date: Mon, 17 Feb 2020 14:36:58 +0000 [thread overview]
Message-ID: <CAFEAcA-RnKYfJRaGDSFFx=O17mdvsPMEwbfQ1prTrhmrosAGHQ@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA--P9FLM4qBxf23sLuv5Tz4HRgj7ONC7ODxnfZiLph9TA@mail.gmail.com>
On Fri, 7 Feb 2020 at 11:50, Peter Maydell <peter.maydell@linaro.org> wrote:
> but some of our documentation has always been a bit of an awkward
> fit into this classification:
> * qemu-img
> * qemu-nbd
> * virtfs-proxy-helper
> etc. I've tended to put these things into interop/.
>
> The proposal from Dan and David was that we should add a sixth
> top-level manual
> * QEMU Tools Guide (docs/tools)
>
> which would be a more coherent place for these to live.
OK, consensus seems to be that this is a good idea. Here's
what I specifically intend to move:
docs/interop/qemu-img.rst
docs/interop/qemu-nbd.rst
docs/interop/virtfs-proxy-helper.rst
docs/interop/qemu-trace-stap.rst
docs/interop/virtiofsd.rst
Nothing else (in particular including qemu-ga.rst) moves;
none of the as-yet unconverted documents need to move either.
thanks
-- PMM
next prev parent reply other threads:[~2020-02-17 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 11:50 should we have a new 'tools' manual? Peter Maydell
2020-02-07 11:59 ` Daniel P. Berrangé
2020-02-07 12:37 ` Paolo Bonzini
2020-02-07 14:32 ` Eric Blake
2020-02-07 14:42 ` Paolo Bonzini
2020-02-07 15:24 ` Dr. David Alan Gilbert
2020-02-17 14:36 ` Peter Maydell [this message]
2020-02-17 14:48 ` Aleksandar Markovic
2020-02-17 15:01 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2020-02-11 21:15 G 3
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-RnKYfJRaGDSFFx=O17mdvsPMEwbfQ1prTrhmrosAGHQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--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).