From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH 0/3] docs: Create a 'tools' manual
Date: Mon, 17 Feb 2020 17:04:47 +0100 [thread overview]
Message-ID: <1865c4e9-a0b5-0c50-adb8-e46da1b0d8a9@redhat.com> (raw)
In-Reply-To: <20200217155415.30949-1-peter.maydell@linaro.org>
On 17/02/20 16:54, Peter Maydell wrote:
> This patchset creates the new 'tools' manual that we've
> decided we should have, and moves 5 existing documents to it:
>
> 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
>
> This change will conflict with the QAPI-doc-comment-to-rST
> patchset because they both change the docs/interop makefile
> rules, but I expect this one to get in to master first;
> the other needs a respin at some point anyhow.
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
We can move them back to the system manual once it's converted to rST,
but for now it's the best solution.
(In fact, I am willing to do the conversion from texi to rST if: 1)
someone else helps with the .hx parts; 2) we accept that the current
structure of the manual isn't great but we agree to reorganize
everything after the conversion).
Paolo
next prev parent reply other threads:[~2020-02-17 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 15:54 [PATCH 0/3] docs: Create a 'tools' manual Peter Maydell
2020-02-17 15:54 ` [PATCH 1/3] docs: Create new " Peter Maydell
2020-02-17 15:54 ` [PATCH 2/3] docs: Move qemu-option-trace.rst.inc to docs/ Peter Maydell
2020-02-17 15:54 ` [PATCH 3/3] docs: Move tools documentation to tools manual Peter Maydell
2020-02-17 18:24 ` Dr. David Alan Gilbert
2020-02-17 18:41 ` Paolo Bonzini
2020-02-17 19:19 ` Peter Maydell
2020-02-17 16:00 ` [PATCH 0/3] docs: Create a 'tools' manual Richard Henderson
2020-02-17 16:04 ` Paolo Bonzini [this message]
2020-02-17 16:18 ` Peter Maydell
2020-02-17 16:29 ` Paolo Bonzini
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=1865c4e9-a0b5-0c50-adb8-e46da1b0d8a9@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@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).