From: Jeff Cody <jcody@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Updating documentation at http://wiki.qemu.org/download/qemu-doc.html
Date: Tue, 26 Apr 2016 08:37:55 -0400 [thread overview]
Message-ID: <20160426123755.GC7299@localhost.localdomain> (raw)
In-Reply-To: <20160426100245.GH10650@stefanha-x1.localdomain>
On Tue, Apr 26, 2016 at 11:02:45AM +0100, Stefan Hajnoczi wrote:
> On Tue, Apr 26, 2016 at 07:50:31AM +0100, Mark Cave-Ayland wrote:
> > Does anyone know if it's possible to update the documentation at the
> > above URL? It appears as a link at http://wiki.qemu-project.org/Manual
> > and seems to be the first hit for most people looking for information on
> > QEMU SPARC emulation, which is frustrating as the information there is
> > well out of date. Presumably this is because the documentation is hosted
> > on the qemu.org domain itself and so ranks higher?
>
> Hi Mark,
> I've CCed Jeff Cody, who is taking over as system administrator for
> QEMU. The http://wiki.qemu.org/download/qemu-doc.html link is just a
> static page from 2010.
>
> It should be possible to rebuild the HTML docs and replace the file.
> Even better would be to update it from a cron job.
>
> Stefan
Thanks.
I've update the qemu-doc.html at the above link with the latest output of
"make qemu-doc.html" from git master. I'll set up a daily cronjob to take care
of that automatically, as well.
Jeff
next prev parent reply other threads:[~2016-04-26 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 6:50 [Qemu-devel] Updating documentation at http://wiki.qemu.org/download/qemu-doc.html Mark Cave-Ayland
2016-04-26 10:02 ` Stefan Hajnoczi
2016-04-26 12:37 ` Jeff Cody [this message]
2016-04-26 23:09 ` Mark Cave-Ayland
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=20160426123755.GC7299@localhost.localdomain \
--to=jcody@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.