qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH 0/4] docs: Miscellaneous rST conversions
Date: Tue, 25 Feb 2020 18:01:17 +0100	[thread overview]
Message-ID: <5a6757cb-fda2-ba3f-6c24-f09829faf4ab@redhat.com> (raw)
In-Reply-To: <20200225154121.21116-1-peter.maydell@linaro.org>

On 25/02/20 16:41, Peter Maydell wrote:
> This patchset converts some texi files used in qemu-doc.texi to rST:
> 
>  * docs/security.texi
>  * qemu-tech.texi
>  * qemu-deprecated.texi
> 
> which all end up as sections of the "system" manual.
> 
> In all cases, these pieces of the documentation are part of
> the qemu-doc HTML file, but not included in the qemu.1 manpage,
> so they are just a straightforward format conversion.
> 
> security and deprecated are pure conversions with only
> changes to the formatting, not to the contents.
> 
> For qemu-tech.texi, a large part of it was an extremely out of
> date and partial attempt to document the limitations of our
> CPU emulation. Apart from a change to the Xtensa section in
> 2012, no part of the actual text seems to have been updated
> since 2008. I judged it better to simply dump this rather
> than carry it over. Creating an actually accurate section
> about the limitations of the various guest architectures
> is probably easier done from scratch if we want it and are
> prepared to actually keep it up to date this time...

I assume these are not meant to be applied now, except patch 2?
For what it's worth, security.texi can be converted just fine with:

makeinfo -o - --docbook security.texi  | pandoc -f docbook -t rst

Paolo



  parent reply	other threads:[~2020-02-25 17:07 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 ` Paolo Bonzini [this message]
2020-02-25 17:11   ` [PATCH 0/4] docs: Miscellaneous rST conversions 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
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=5a6757cb-fda2-ba3f-6c24-f09829faf4ab@redhat.com \
    --to=pbonzini@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).