From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 0/2] vnc patch queue
Date: Wed, 10 Dec 2014 10:32:18 +0100 [thread overview]
Message-ID: <1418203940-5421-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Starting to flush queues after the 2.2 release, starting with two little
vnc fixes. Well, keymap is strictly speaking not vnc, but vnc is the
major user of keymap support, so I sticked it in here.
please pull,
Gerd
The following changes since commit 45e1611de8be0eae55967694dd6e627c2dc354f2:
Update version for v2.2.0 release (2014-12-09 12:13:37 +0000)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-vnc-20141210-1
for you to fetch changes up to 43948386bb109b97b3de0bb48573f317bdcb5008:
keymaps: correct keymaps.c following Qemu coding style (2014-12-10 10:08:12 +0100)
----------------------------------------------------------------
vnc-enc-tight fix, keymaps code style.
----------------------------------------------------------------
Gonglei (2):
vnc-enc-tight: fix Arguments in wrong order
keymaps: correct keymaps.c following Qemu coding style
ui/keymaps.c | 196 +++++++++++++++++++++++++++++------------------------
ui/vnc-enc-tight.c | 2 +-
2 files changed, 109 insertions(+), 89 deletions(-)
next reply other threads:[~2014-12-10 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 9:32 Gerd Hoffmann [this message]
2014-12-10 9:32 ` [Qemu-devel] [PULL 1/2] vnc-enc-tight: fix Arguments in wrong order Gerd Hoffmann
2014-12-10 9:32 ` [Qemu-devel] [PULL 2/2] keymaps: correct keymaps.c following Qemu coding style Gerd Hoffmann
2014-12-11 11:40 ` [Qemu-devel] [PULL 0/2] vnc patch queue Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2014-10-28 10:59 Gerd Hoffmann
2014-10-30 19:11 ` Peter Maydell
2014-09-18 6:33 Gerd Hoffmann
2014-09-18 18:30 ` Peter Maydell
2014-07-01 11:33 Gerd Hoffmann
2014-07-01 15:16 ` 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=1418203940-5421-1-git-send-email-kraxel@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).