From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH 0/4] docs: Miscellaneous rST conversions
Date: Tue, 25 Feb 2020 22:32:45 +0000 [thread overview]
Message-ID: <CAFEAcA97fcmgLx_QGgRs1Q8XvWAVVf7ykjfHQ6c0R5xPcq41BA@mail.gmail.com> (raw)
In-Reply-To: <CABgObfY0QY0g42QGB6K_PzKUX8OPhiSe-KXwU+rB9ksK3FzPog@mail.gmail.com>
On Tue, 25 Feb 2020 at 20:10, Paolo Bonzini <pbonzini@redhat.com> wrote:
> The main issue with this series and Kashyap's is that if we don't manage to get
> everything done in 5.0 we have a mutilated qemu-doc. Then either we keep it
> mutilated or we scramble to undo the work. So I would agree to commit the
> series in this order, but without the removal of the .texi files.
Kashyap's set is in the same ballpark as what we've currently
converted (notably it's pretty much equivalent to the qemu-block-drivers
conversion in that it takes what was part of qemu-doc plus a manpage
and turns it into part of the system manual plus a manpage).
It's also the most awkward to try to keep the texi around for, because
the makefile runes for the texi want to generate the manpage too.
So I think I would argue for taking that as-is, including removal of the
texi files.
I agree that it would be good to avoid a half-converted qemu-doc;
if people think keeping two parallel doc files until we're sure we
can do the conversion is useful insurance I'm happy to go along
with that.
If we ended up with "we managed all the conversion except for
the qapi json doc comments parts" would we be ok with having a
qemu-doc.html that just contained those, and all the actual docs
transitioning to rST for this release? Or would we want to roll
back the rST for the main qemu-doc parts too in that situation?
thanks
-- PMM
next prev parent reply other threads:[~2020-02-25 22:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 15:41 [PATCH 0/4] docs: Miscellaneous rST conversions Peter Maydell
2020-02-25 15:41 ` [PATCH 1/4] docs: Convert security.texi to rST format Peter Maydell
2020-02-26 11:48 ` Aleksandar Markovic
2020-02-25 15:41 ` [PATCH 2/4] docs: Remove the "CPU emulation" part of the "Implementation notes" Peter Maydell
2020-02-26 11:33 ` Aleksandar Markovic
2020-02-25 15:41 ` [PATCH 3/4] docs: Convert 'managed start up options' docs to rST Peter Maydell
2020-02-26 11:49 ` Aleksandar Markovic
2020-02-25 15:41 ` [PATCH 4/4] docs: Convert qemu-deprecated.texi " Peter Maydell
2020-02-26 0:33 ` Alistair Francis
2020-02-26 11:24 ` Aleksandar Markovic
2020-02-25 17:01 ` [PATCH 0/4] docs: Miscellaneous rST conversions Paolo Bonzini
2020-02-25 17:11 ` Peter Maydell
2020-02-25 17:48 ` Paolo Bonzini
2020-02-25 17:59 ` Peter Maydell
2020-02-25 18:28 ` Paolo Bonzini
2020-02-25 18:56 ` Peter Maydell
2020-02-25 19:10 ` Paolo Bonzini
2020-02-25 19:50 ` Peter Maydell
2020-02-25 20:09 ` Paolo Bonzini
2020-02-25 22:32 ` Peter Maydell [this message]
2020-02-26 7:50 ` Markus Armbruster
2020-02-26 8:40 ` 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=CAFEAcA97fcmgLx_QGgRs1Q8XvWAVVf7ykjfHQ6c0R5xPcq41BA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--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).