From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] May I get a document about detailed architecture of QEMU
Date: Thu, 28 Aug 2008 22:09:08 -0500 [thread overview]
Message-ID: <48B76854.50907@codemonkey.ws> (raw)
In-Reply-To: <fdaac4d50808281852v50de4059j1c1b7527cbb0f2c0@mail.gmail.com>
Jun Koi wrote:
> On Fri, Aug 29, 2008 at 10:47 AM, Jun Koi <junkoi2004@gmail.com> wrote:
>
>
> And to update information about new features, how about having a blog
> for community/developers of QEMU? Like what Xen is doing now.
>
I'd rather developers spent their time writing code. There is more than
enough info on the mailing list, discussed in #qemu on IRC, and within
the code. You just have to put the time into digging it up.
Regards,
Anthony Liguori
> http://blog.qemu.org, for example.
>
> Thanks,
> J
>
>
>
next prev parent reply other threads:[~2008-08-29 3:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 8:47 [Qemu-devel] May I get a document about detailed architecture of QEMU linemin2001
2008-08-29 1:39 ` Mulyadi Santosa
2008-08-29 1:45 ` Paul Brook
2008-08-29 1:47 ` Jun Koi
2008-08-29 1:52 ` Jun Koi
2008-08-29 3:09 ` Anthony Liguori [this message]
2008-08-29 2:01 ` Mulyadi Santosa
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=48B76854.50907@codemonkey.ws \
--to=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).