qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Eduardo Habkost <ehabkost@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
	Gabriel Barreto <sbarreto.gabriel@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	"Emilio G. Cota" <cota@braap.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Cleber Rosa <crosa@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] Introducing GSoC project: API Documentation Generation
Date: Tue, 21 May 2019 13:01:38 +0200	[thread overview]
Message-ID: <34f9ddb5-a4b2-e8ed-ba10-f43036276d4b@redhat.com> (raw)
In-Reply-To: <CAFEAcA_jn6VBHMoKoGRojGTEQXOyzLtPG-rCE+uAt3BDBxYOBw@mail.gmail.com>

On 21/05/19 11:42, Peter Maydell wrote:
> (The other interesting thing I'd wondered about with generation
> of docs from code comments is whether we would get better
> (ie more accurate, regularly updated) documentation of our
> supported machine models if we generated those parts of the
> docs from comments. But that's definitely much harder than just
> getting API documentation, because it involves trying to
> integrate them into a 'user documentation' manual which we
> have not yet converted from texinfo.)

For the user documentation, makeinfo can produce docbook, and that seems
to be the best way to convert out of Texinfo.  At that point you can
either pass docbook to sphinx (see
https://wiki.qemu.org/Features/Documentation though it's a bit out of
date), or convert it to rST using Pandoc.

Paolo


      reply	other threads:[~2019-05-21 11:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 18:41 [Qemu-devel] Introducing GSoC project: API Documentation Generation Eduardo Habkost
2019-05-20 18:48 ` John Snow
2019-05-21  8:53 ` Daniel P. Berrangé
2019-05-21  9:43   ` Peter Maydell
2019-05-21 11:06     ` Daniel P. Berrangé
2019-05-21 10:55   ` Paolo Bonzini
2019-05-21 15:18     ` Markus Armbruster
2019-05-21 15:25       ` Daniel P. Berrangé
2019-05-21 15:27       ` Peter Maydell
2019-05-21 17:14         ` Paolo Bonzini
2019-05-21 20:32         ` John Snow
2019-05-21 20:37           ` Eduardo Habkost
2019-05-22  8:20             ` Paolo Bonzini
2019-05-23 12:20               ` John Snow
2019-05-24 18:34                 ` Paolo Bonzini
2019-05-24 19:08                   ` Eduardo Habkost
2019-05-24 20:02                     ` Paolo Bonzini
2019-05-21 16:17     ` Eduardo Habkost
2019-05-21 17:14       ` Paolo Bonzini
2019-05-21  9:42 ` Peter Maydell
2019-05-21 11:01   ` Paolo Bonzini [this message]

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=34f9ddb5-a4b2-e8ed-ba10-f43036276d4b@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@redhat.com \
    --cc=cota@braap.org \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sbarreto.gabriel@gmail.com \
    --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).