From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"John Snow" <jsnow@redhat.com>,
qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: QEMU HTML documentation now on qemu.org
Date: Thu, 7 Nov 2019 10:06:06 +0000 [thread overview]
Message-ID: <20191107100606.GA120292@redhat.com> (raw)
In-Reply-To: <20191106161928.GA353373@stefanha-x1.localdomain>
On Wed, Nov 06, 2019 at 05:19:28PM +0100, Stefan Hajnoczi wrote:
> Hi,
> You can now access the latest QEMU HTML documentation built from
> qemu.git/master nightly at:
>
> https://wiki.qemu.org/docs/qemu-doc.html
> https://wiki.qemu.org/docs/qemu-qmp-ref.html
> https://wiki.qemu.org/docs/qemu-ga-ref.html
> ...as well as interop/ and specs/
>
> Feel free to link to the documentation from the QEMU website and/or
> wiki!
What's the reason for putting on wiki.qemu.org URL ? It feels like
having it under www.qemu.org would be a more natural home, especially
if we can then make it pick up the jekyll theme around the pages.
Ideally we should publish the docs under versioned URL when we
make a release. eg /docs/latest/.... for current GIT master
which I presume the above is tracking, and then a /docs/$VERSION/...
for each major release we cut.
That way users can get an accurate view of features in the QEMU
they are actually using.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-11-07 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 16:19 QEMU HTML documentation now on qemu.org Stefan Hajnoczi
2019-11-07 9:29 ` Stefan Hajnoczi
2019-11-07 16:04 ` Peter Maydell
2019-11-07 10:06 ` Daniel P. Berrangé [this message]
2019-11-07 15:44 ` Stefan Hajnoczi
2019-11-07 16:01 ` Daniel P. Berrangé
2019-11-08 8:41 ` Stefan Hajnoczi
2019-11-08 9:29 ` Paolo Bonzini
2019-11-08 9:45 ` Daniel P. Berrangé
[not found] <mailman.2098.1573202511.13329.qemu-devel@nongnu.org>
2019-11-15 14:05 ` G 3
2019-11-21 12:51 ` 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=20191107100606.GA120292@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--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).