From: "Christian MICHON" <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Problem: Keyboard dead after "-loadvm"
Date: Mon, 17 Jul 2006 23:28:40 +0200 [thread overview]
Message-ID: <46d6db660607171428i6ac08754q55f621c78bbed25e@mail.gmail.com> (raw)
In-Reply-To: <44BBE6DE.9080200@bellard.org>
On 7/17/06, Fabrice Bellard <fabrice@bellard.org> wrote:
> Sometimes I try :-) But evaluating patches takes a large amount of time
> and in a program like QEMU regressions are difficult to track and very
> easy to introduce...
>
not all on this list do contribute patches (in my case, not much
contribution at this level). But I believe we're tons of testers of
incoming patches :)
you're not alone to test these patches: this is what I mean...
I remember the asynchronous/dma patch could be also a good
candidate for insertion, if it could be updated...
--
Christian
next prev parent reply other threads:[~2006-07-17 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 9:18 [Qemu-devel] Problem: Keyboard dead after "-loadvm" Carsten Thorenz
2006-07-17 10:19 ` Johannes Schindelin
2006-07-17 14:01 ` Carsten Thorenz
2006-07-17 19:37 ` Fabrice Bellard
2006-07-17 21:28 ` Christian MICHON [this message]
2006-07-17 22:01 ` [Qemu-devel] " Anthony Liguori
2006-07-17 22:19 ` 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=46d6db660607171428i6ac08754q55f621c78bbed25e@mail.gmail.com \
--to=christian.michon@gmail.com \
--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).