From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [qemu-web PATCH] documentation: update links to readthedocs
Date: Mon, 3 Feb 2020 12:54:47 +0100 [thread overview]
Message-ID: <82f0aa8e-b445-ad7f-1b17-03f4bb180a85@redhat.com> (raw)
In-Reply-To: <CAFEAcA9Q5nsD5iTPwsVVx73HPUD6aGKd0Sf2FUkAFqjAZhGMGw@mail.gmail.com>
On 03/02/2020 12.46, Peter Maydell wrote:
> On Wed, 15 Jan 2020 at 11:11, Stefan Hajnoczi <stefanha@redhat.com> wrote:
>> The qemu.git/master docs are built nightly here (index.html is now
>> visible!):
>> https://www.qemu.org/docs/master/
>>
>> qemu.org's docs are more useful at the moment since they include the
>> user documentation in addition to the developer documentation.
>
> Our top-level documentation page https://www.qemu.org/documentation/
> still points to https://qemu.weilnetz.de/qemu-doc.html -- should
> we update that now to link to https://www.qemu.org/docs/master/
> instead ?
Sure, but I'm still waiting for someone to suggest a final patch here.
Open questions:
- Do we also want to link to readthedocs as suggested by Alex, or is our
own docs on www.qemu.org enough?
- Do we still want to link to weilnetz.de (as it was the case with
StefanH's original patch https://patchwork.kernel.org/patch/11234545/)
or should that link be removed?
- Do we only link to https://www.qemu.org/docs/master/ or shall we
link to the individual docs (qemu-doc, qemu-qmp-ref, ...) ?
Thomas
next prev parent reply other threads:[~2020-02-03 11:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 10:35 [qemu-web PATCH] documentation: update links to readthedocs Alex Bennée
2020-01-14 11:04 ` Stefan Hajnoczi
2020-01-14 11:11 ` Thomas Huth
2020-01-15 11:10 ` Stefan Hajnoczi
2020-01-15 11:56 ` Alex Bennée
2020-01-15 12:01 ` Daniel P. Berrangé
2020-01-20 10:16 ` Stefan Hajnoczi
2020-01-20 10:31 ` Peter Maydell
2020-02-03 11:46 ` Peter Maydell
2020-02-03 11:54 ` Thomas Huth [this message]
2020-02-03 12:07 ` Peter Maydell
2020-02-03 12:12 ` Thomas Huth
2020-02-03 12:38 ` Peter Maydell
2020-02-03 12:44 ` Peter Maydell
2020-02-03 12:46 ` Thomas Huth
2020-02-03 13:21 ` Thomas Huth
2020-02-05 10:28 ` Stefan Hajnoczi
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=82f0aa8e-b445-ad7f-1b17-03f4bb180a85@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=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).