From: Riku Voipio <riku.voipio@iki.fi>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Call for help in reviewing patches (!kvm & linux-user)
Date: Thu, 15 Apr 2010 08:25:53 +0000 [thread overview]
Message-ID: <20100415082553.GA19788@afflict.kos.to> (raw)
In-Reply-To: <20100414233217.GD17857@hall.aurel32.net>
On Thu, Apr 15, 2010 at 01:32:17AM +0200, Aurelien Jarno wrote:
> My impression is that few persons have interest in linux-user or
> non-KVM targets areas, at least from the development point of view.
> I personally don't care about linux-user code, though I have tried to
> merge patches in this area anyway, as otherwise they are just
> bitrotting on the mailing list.
I'll increase my effort on reviewing and testing linux-user patches once
I have a bit more time.
Riku
prev parent reply other threads:[~2010-04-15 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 23:32 [Qemu-devel] Call for help in reviewing patches (!kvm & linux-user) Aurelien Jarno
2010-04-15 0:08 ` [Qemu-devel] " Paolo Bonzini
2010-04-15 0:19 ` Alexander Graf
2010-04-15 0:28 ` Paolo Bonzini
2010-04-15 8:25 ` Riku Voipio [this message]
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=20100415082553.GA19788@afflict.kos.to \
--to=riku.voipio@iki.fi \
--cc=aurelien@aurel32.net \
--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).