From: Scott Tsai <scottt.tw@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] wiki.qemu.org
Date: Sat, 30 Jan 2010 04:23:20 +0800 [thread overview]
Message-ID: <ef2f888d1001291223o2f060df2lf4258a00a993d50b@mail.gmail.com> (raw)
In-Reply-To: <4B633A80.100@codemonkey.ws>
On Sat, Jan 30, 2010 at 3:44 AM, Anthony Liguori <anthony@codemonkey.ws> wrote:
> Hi,
>
> I've been (slowly) working to convert qemu.org to a wiki in order to allow
> more community participation in the website. I've finally got a site setup
> and to my liking with all of the www.qemu.org content migrated.
>
> Before doing the switch, I need to figure out what to do with the current
> texi documentation. I think it makes sense to move qemu-doc.texi to a wiki
> page and remove it from the source repository. The other option would be to
> link to it as an external page and keep it within revision control.
>
> Does anyone have strong opinions one way or another?
To keep the code and documentation in sync, I suggest keeping the
portion generated from
qemu-img-cmds.hx, qemu-monitor.hx and qemu-options.hx in texinfo
format under revision control.
This encourages updating the documentation in the same patch that adds
new options and monitor commands.
The "QEMU System emulator for non PC targets" section in qemu-doc.texi
seems rather qemu version dependent as well? If true, moving this
information to a wiki risks the documentation not matching the qemu
version installed on users' machines.
next prev parent reply other threads:[~2010-01-29 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 19:44 [Qemu-devel] [RFC] wiki.qemu.org Anthony Liguori
2010-01-29 20:23 ` Scott Tsai [this message]
2010-01-29 20:29 ` Andreas Färber
2010-01-29 20:53 ` Anthony Liguori
2010-01-29 21:47 ` Stefan Weil
2010-01-29 22:35 ` Anthony Liguori
2010-02-25 13:50 ` Paul Brook
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=ef2f888d1001291223o2f060df2lf4258a00a993d50b@mail.gmail.com \
--to=scottt.tw@gmail.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
/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).