From: 陳韋任 <chenwj@iis.sinica.edu.tw>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org,
KVM devel mailing list <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for May, Tuesday 8th
Date: Mon, 7 May 2012 21:22:58 +0800 [thread overview]
Message-ID: <20120507132258.GA44195@cs.nctu.edu.tw> (raw)
In-Reply-To: <4FA7C71C.9090003@codemonkey.ws>
> - QEMU documentation
>
> qemu-doc.texi is in a pretty awful state. I'm wondering if anyone has any ideas
> about how we can improve it. One thing we could do is move the entire contents
> of it to the wiki to allow for broader editing.
What's qemu-tech.texi status? ;)
> I'd also be really happy to have a documentation submaintainer if anyone is
> interested in the role. Other ideas?
IMHO, one of the problem is there are documents scattering out there, not just
in one place. There are too many links on http://wiki.qemu.org/Manual. :/ If
people can focus on one document, then it's easier to make it a good shape.
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
Homepage: http://people.cs.nctu.edu.tw/~chenwj
next prev parent reply other threads:[~2012-05-07 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 11:47 [Qemu-devel] KVM call agenda for May, Tuesday 8th Juan Quintela
2012-05-07 12:54 ` Anthony Liguori
2012-05-08 14:10 ` Andreas Färber
2012-05-08 14:24 ` Anthony Liguori
2012-05-08 14:53 ` Andreas Färber
2012-05-08 15:13 ` Andreas Färber
2012-05-08 15:32 ` Anthony Liguori
2012-05-07 12:59 ` Anthony Liguori
2012-05-07 13:22 ` 陳韋任 [this message]
2012-05-08 12:14 ` Anthony Liguori
2012-05-08 12:22 ` Alexander Graf
2012-05-08 13:39 ` Luiz Capitulino
2012-05-08 13:53 ` Juan Quintela
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=20120507132258.GA44195@cs.nctu.edu.tw \
--to=chenwj@iis.sinica.edu.tw \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).