From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kwolf@redhat.com, shaharh@gmail.com, qemu-devel@nongnu.org,
Dustin Kirkland <kirkland@canonical.com>
Subject: Re: [Qemu-devel] Re: Qemu does not pass pressed caps lock to client
Date: Fri, 12 Feb 2010 12:44:35 -0600 [thread overview]
Message-ID: <4B75A193.8040202@codemonkey.ws> (raw)
In-Reply-To: <4B759B57.8010201@redhat.com>
On 02/12/2010 12:17 PM, Paolo Bonzini wrote:
> On 02/12/2010 04:15 PM, Anthony Liguori wrote:
>>
>> So basically, Debian carries a hacked version of SDL that changes the
>> key press behaviour?
>
> Yes, the patch was submitted to not change the default but the
> maintainer thought he knew better. Or confused an == with a != more
> likely.
>
>> That's a Debian/Ubuntu bug. Shame on them for changing the behaviour of
>> a library API like that.
>
> Indeed. Maybe the Debian/Ubuntu maintainers for QEMU and KVM will
> read this thread and make a fuss.
I've already updated the bug report appropriately. Dustin, the ball's
in your court :-)
> The only reason it is interesting, is that QEMU is actually going
> through efforts to get the same behavior that the Debian/Ubuntu change
> implements (get a press and a release event whenever you toggle Caps
> Lock).
Yes, but the problem with
> Paolo
next prev parent reply other threads:[~2010-02-12 18:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 21:13 [Qemu-devel] Qemu does not pass pressed caps lock to client Shahar Havivi
2010-02-12 9:54 ` Kevin Wolf
2010-02-12 11:09 ` Shahar Havivi
2010-02-12 11:43 ` Kevin Wolf
2010-02-12 12:39 ` [Qemu-devel] " Paolo Bonzini
2010-02-12 15:15 ` Anthony Liguori
2010-02-12 18:17 ` Paolo Bonzini
2010-02-12 18:44 ` Anthony Liguori [this message]
2010-02-12 20:49 ` Dustin Kirkland
2010-02-13 11:21 ` Paolo Bonzini
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=4B75A193.8040202@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kirkland@canonical.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shaharh@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.