From: John Snow <jsnow@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] Sketch of a transition of QEMU docs to Sphinx
Date: Tue, 11 Jun 2019 13:36:21 -0400 [thread overview]
Message-ID: <19821e20-b7a1-e3ea-364b-251e256e913c@redhat.com> (raw)
In-Reply-To: <877e9stw9p.fsf@dusky.pond.sub.org>
On 6/11/19 3:29 AM, Markus Armbruster wrote:
> Peter Maydell <peter.maydell@linaro.org> writes:
>
>> On Tue, 21 May 2019 at 19:56, Peter Maydell <peter.maydell@linaro.org> wrote:
>>>
>>> Currently we have a vague plan that we should migrate our
>>> documentation away from Texinfo to using Sphinx, plus some isolated
>>> bits of documentation already in .rst format. This email is an attempt
>>> to sketch out a transition plan for getting us from where we are today
>>> to where (I think) we want to be.
>>
>> Since nobody seemed to disagree particularly with this sketch,
>
> I don't think rST is an improvement over Texinfo. As Paolo said, it's
> the Perl of ASCII-based markups. But I (reluctantly) agree with Paolo
> that our current mix of Texinfo, rST, Markdown, and ad hoc markup is
> worse than consistent use of one markup system, even if it's an
> ill-conceived one like rST.
>
> March of progress, I guess.
>
> [...]
>
I will say that at a minimum I enjoy the combination of sphinx and rST
because at least we can error out on warnings and check that the cross
references are valid.
Markdown is a hot mess of a non-spec that is subtly different for just
about every implementation, and we procedurally check none of ours.
At least rST is one thing, I guess. And that it's extensible via sphinx
is nice.
--js
prev parent reply other threads:[~2019-06-11 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 18:56 [Qemu-devel] Sketch of a transition of QEMU docs to Sphinx Peter Maydell
2019-05-28 19:09 ` John Snow
2019-05-28 22:07 ` Peter Maydell
2019-06-07 17:37 ` Peter Maydell
2019-06-11 7:29 ` Markus Armbruster
2019-06-11 17:36 ` John Snow [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=19821e20-b7a1-e3ea-364b-251e256e913c@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).