From: Thomas Huth <thuth@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Daniel Berrange <berrange@redhat.com>,
Stefan Weil <sw@weilnetz.de>
Subject: Re: [qemu-web PATCH v3] documentation: link to nightly documentation
Date: Tue, 12 Nov 2019 13:09:08 +0100 [thread overview]
Message-ID: <3fa14fbe-32e1-9bed-2557-428343deedd1@redhat.com> (raw)
In-Reply-To: <20191108105435.403161-1-stefanha@redhat.com>
On 08/11/2019 11.54, Stefan Hajnoczi wrote:
> Link to the documentation built from qemu.git/master once a day.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> v3:
> * Use a qemu.org URL, not a wiki.qemu.org URL [danpb]
> v2:
> * This revision was broken - please ignore! :)
> ---
> documentation.md | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/documentation.md b/documentation.md
> index f4ef9f4..5198e02 100644
> --- a/documentation.md
> +++ b/documentation.md
> @@ -3,6 +3,8 @@ title: QEMU documentation
> permalink: /documentation/
> ---
>
> +The latest development version documentation is available [here](https://qemu.org/docs/master/index.html).
> +
> The [QEMU user manual](https://qemu.weilnetz.de/qemu-doc.html) can be read online, courtesy of Stefan Weil.
I assume your generated docs will also contain the qemu-doc.html for the
users? Should we then remove the link to weilnetz here?
> More documentation is found in the <a href="https://git.qemu.org/?p=qemu.git;a=tree;f=docs;hb=master">`docs`</a>
> directory of the QEMU git tree.
Do we still need the link to the docs folder in the git repo after your
changes?
Thomas
prev parent reply other threads:[~2019-11-12 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 10:54 [qemu-web PATCH v3] documentation: link to nightly documentation Stefan Hajnoczi
2019-11-08 10:56 ` Daniel P. Berrangé
2019-11-12 12:09 ` Thomas Huth [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=3fa14fbe-32e1-9bed-2557-428343deedd1@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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).