From: Paolo Bonzini <pbonzini@redhat.com>
To: "Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org
Cc: Stefan Weil <sw@weilnetz.de>, Jeff Cody <codyprime@gmail.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [qemu-web PATCH] Import historical documentation
Date: Thu, 6 Dec 2018 21:01:46 +0100 [thread overview]
Message-ID: <86756391-b9b7-12d0-f6ec-8766ea7ab4d7@redhat.com> (raw)
In-Reply-To: <08d36eda-e8e7-4ece-edc5-ef436d25e6b7@redhat.com>
On 04/12/18 11:56, Thomas Huth wrote:
> I think it would be best if we find a way to automate this process, e.g.
> when a new release is tagged, a script generates the docs and puts them
> somewhere on the web server, into the right new folder based on the name
> of the tag. However, I don't know the qemu server well enough to know
> whether that's possible or not ... maybe Jeff or Paolo can comment on
> this...
There are two possibilities: putting the docs on download.qemu.org and
going for Marc-André's styling solution, or using a dash of sed to
remove the <head> and use Jekyll to generate the page.
Either way, there isn't much to do on the webserver side, so a better
person to ask would be Mike Roth as he's the Guy Who Does The Releases.
For either solution he'd have to build the documentation and scp it (if
we go for download.qemu.org) or commit it to qemu-web.git (if we go for
Jekyll). I guess he has scripts already to automate part of the release
process, but I have no idea if the website update is automated already.
Paolo
next prev parent reply other threads:[~2018-12-06 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 16:41 [Qemu-devel] [qemu-web PATCH] Import historical documentation Daniel P. Berrangé
2018-12-03 19:14 ` Marc-André Lureau
2018-12-04 10:19 ` Daniel P. Berrangé
2018-12-04 10:56 ` Thomas Huth
2018-12-06 20:01 ` Paolo Bonzini [this message]
2018-12-07 9:44 ` Daniel P. Berrangé
2018-12-07 15:59 ` Michael Roth
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=86756391-b9b7-12d0-f6ec-8766ea7ab4d7@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=codyprime@gmail.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
--cc=thuth@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).