From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P. Berrange" <berrange@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [RFC PATCH] docs/devel: re-organise the developers guide into sections
Date: Wed, 24 Feb 2021 10:39:04 -0300 [thread overview]
Message-ID: <a0164e59-cc94-976a-a804-1c0c7c51f89a@redhat.com> (raw)
In-Reply-To: <CAFEAcA8kt_vsHFHGL=dQMPBqogJTQOiAV=O-Zc=UBxQ5AR7opA@mail.gmail.com>
On 2/24/21 10:15 AM, Peter Maydell wrote:
> On Wed, 24 Feb 2021 at 12:51, Wainer dos Santos Moschetta
> <wainersm@redhat.com> wrote:
>> Just a fyi... yesterday I realized that the (current) TOC is not getting
>> rendered on my Firefox (or chrome) browser:
>>
>> https://gitlab.com/qemu-project/qemu/-/tree/master/docs/devel
> That's the source code for the docs, isn't it? gitlab
> is trying to render it as raw rst, but that won't handle
> all the Sphinx-specific markup, including the TOC.
You're right Peter. For one second I thought gitlab was able to render
the rst files.
>
> The built-and-rendered docs are elsewhere (the gitlab CI
> job runs Sphinx and puts the rendered manuals here):
> https://qemu-project.gitlab.io/qemu/
>
> thanks
> -- PMM
>
prev parent reply other threads:[~2021-02-24 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 10:51 [RFC PATCH] docs/devel: re-organise the developers guide into sections Alex Bennée
2021-02-23 11:13 ` Peter Maydell
2021-02-24 11:57 ` Stefan Hajnoczi
2021-02-24 12:51 ` Wainer dos Santos Moschetta
2021-02-24 13:15 ` Peter Maydell
2021-02-24 13:39 ` Wainer dos Santos Moschetta [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=a0164e59-cc94-976a-a804-1c0c7c51f89a@redhat.com \
--to=wainersm@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--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).