From: Paolo Bonzini <pbonzini@redhat.com>
To: "Stefan Hajnoczi" <stefanha@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Stefan Hajnoczi" <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Michael Roth" <mdroth@linux.vnet.ibm.com>,
"John Snow" <jsnow@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: QEMU HTML documentation now on qemu.org
Date: Fri, 8 Nov 2019 10:29:36 +0100 [thread overview]
Message-ID: <7361f6d8-e60c-e8ba-cb4c-9b4ec89e3c16@redhat.com> (raw)
In-Reply-To: <20191108084130.GA375005@stefanha-x1.localdomain>
On 08/11/19 09:41, Stefan Hajnoczi wrote:
>> If we're not storing the generated docs in git, then when
>> pushing to qemu-web.git we need to ensure we preserve the
>> extra /docs dir content in some manner.
> For qemu.git/master the built docs might change every day. Committing
> them to qemu-web.git seems like overkill. I'll send a documentation.md
> patch for qemu-web.git instead that simply links to
> wiki.qemu.org/docs/.
I think this is a good first step. Perhaps in the long term we want to
have docs.qemu.org/latest/ link to the latest release,
docs.qemu.org/unstable/ rebuilt from master, etc.
Paolo
next prev parent reply other threads:[~2019-11-08 9:32 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é
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 [this message]
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=7361f6d8-e60c-e8ba-cb4c-9b4ec89e3c16@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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).