From: Gerd Hoffmann <kraxel@redhat.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/3] Ui 20170728 patches
Date: Fri, 28 Jul 2017 15:20:49 +0200 [thread overview]
Message-ID: <1501248049.10943.16.camel@redhat.com> (raw)
In-Reply-To: <20170728125935.18167-1-kraxel@redhat.com>
Hi,
> ui: more keymap fixes for 2.10
Rushing things a bit, because I'm about to disappear into my summer
vacation, so I want get the fixes out of the door.
This is just incremental fixes to yesterdays (somewhat rushed too) pull
request, so I don't expect more problems. Should that not be the case:
Daniel, can you take care while I'm offline?
thanks,
Gerd
next prev parent reply other threads:[~2017-07-28 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 12:59 [Qemu-devel] [PULL 0/3] Ui 20170728 patches Gerd Hoffmann
2017-07-28 12:59 ` [Qemu-devel] [PULL 1/3] ui: correctly detect spice PAUSE scancode sequence Gerd Hoffmann
2017-07-28 12:59 ` [Qemu-devel] [PULL 2/3] ui: drop ac_search and ac_stop Gerd Hoffmann
2017-07-28 12:59 ` [Qemu-devel] [PULL 3/3] ui: add pause key to linux_to_qcode Gerd Hoffmann
2017-07-28 13:20 ` Gerd Hoffmann [this message]
2017-07-28 13:25 ` [Qemu-devel] [PULL 0/3] Ui 20170728 patches Daniel P. Berrange
2017-07-28 14:32 ` Peter Maydell
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=1501248049.10943.16.camel@redhat.com \
--to=kraxel@redhat.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).