From: Riku Voipio <riku.voipio@iki.fi>
To: Erik de Castro Lopo <mle+tools@mega-nerd.com>
Cc: qemu-devel@nongnu.org, Dustin Kirkland <kirkland@canonical.com>
Subject: Re: Re : [Qemu-devel] Cursor keys not working?
Date: Sat, 14 Feb 2009 11:48:55 +0200 [thread overview]
Message-ID: <20090214094855.GA21941@kos.to> (raw)
In-Reply-To: <20090214112435.32d64c9e.mle+tools@mega-nerd.com>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
On Sat, Feb 14, 2009 at 11:24:35AM +1100, Erik de Castro Lopo wrote:
> > > > which also includes a patch:
> > > >
> > > > https://bugzilla.redhat.com/attachment.cgi?id=328839
> > > >
> > > > I applied this patch to svn 6617 and for me it fixed all problems.
> > > >
> > > > Anybody else having similar key binding problems? Anybody looked
> > > > at the above patch for inclusion in Qemu?
> > Yes, someone already submitted this patch. They have been some comments,
> > but no one has addressed them so far.
> If someone can point me to the issues raised, I can see if I can address
> them.
Here:
http://lists.gnu.org/archive/html/qemu-devel/2008-12/msg00469.html
The main issue is the lack of portability of the patch, the secondary issue
is inefficiency. Neither should be hard to fix, the main work goes
into just testing.
--
"rm -rf" only sounds scary if you don't have backups
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-02-14 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 11:17 [Qemu-devel] Cursor keys not working? Rob Landley
2009-02-13 15:24 ` Rick Vernam
2009-02-13 20:30 ` Re : " Sylvain Petreolle
2009-02-13 20:57 ` Aurelien Jarno
2009-02-14 0:24 ` Erik de Castro Lopo
2009-02-14 9:38 ` Rob Landley
2009-02-14 9:48 ` Riku Voipio [this message]
2009-02-14 10:01 ` Re : " Erik de Castro Lopo
2009-02-14 11:45 ` Aurelien Jarno
2009-02-14 11:52 ` Erik de Castro Lopo
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=20090214094855.GA21941@kos.to \
--to=riku.voipio@iki.fi \
--cc=kirkland@canonical.com \
--cc=mle+tools@mega-nerd.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).