From: John Haxby <john.haxby@oracle.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0 of 3][IOEMU] Fix keymap handling for vnc console
Date: Tue, 16 Dec 2008 16:53:43 +0000 [thread overview]
Message-ID: <4947DD17.2070904@oracle.com> (raw)
In-Reply-To: <18753.21308.537159.430285@mariner.uk.xensource.com>
Ian Jackson wrote:
> John Haxby writes ("[Xen-devel] [PATCH 0 of 3][IOEMU] Fix keymap handling for vnc console"):
>
>> This is a slightly updated version of the patch I posted a little while
>> ago. It is a patch against the ioemu-remote tree in xen-3.3-testing.
>> I'll be sending a corresponding patch to qemu-devel when I've got my
>> qemu build environment sorted out.
>>
>
> Thanks. Would you mind if I waited to get this patch via qemu-devel
> and qemu upstream ?
>
>
Yes, that's fine.
> Or at least waited until I see what their response is :-). Obviously
> if they're very tardy I'll consider picking it up directly from you.
>
>
:-)
> I want to pull from qemu-devel again as soon as I've managed to get my
> current tree through our automated tests.
>
I was a little surprised how different upstream qemu was/is. The altgr
and localstate handling that I replaced isn't in upstream qemu at all --
on the other hand they do have exciting things like audio and
cut'n'paste support in there.
I've pushed a suitably modified series of patches to qemu-devel now though.
jch
next prev parent reply other threads:[~2008-12-16 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 16:37 [PATCH 0 of 3][IOEMU] Fix keymap handling for vnc console John Haxby
2008-12-11 16:42 ` [PATCH 1 " John Haxby
2008-12-11 16:43 ` [PATCH 2 " John Haxby
2008-12-11 16:44 ` [PATCH 3 " John Haxby
2008-12-11 17:51 ` [PATCH 0 " Ian Jackson
2008-12-16 16:53 ` John Haxby [this message]
2008-12-16 17:12 ` Ian Jackson
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=4947DD17.2070904@oracle.com \
--to=john.haxby@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.