From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL for-2.0 0/4] gtk: pointer fixes
Date: Mon, 7 Apr 2014 10:56:16 +0200 [thread overview]
Message-ID: <1396860980-7130-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Last minute pointer fixes for gtk. And a MAINTAINERS update
to help ui patches being picked up more timely in the future.
please pull,
Gerd
The following changes since commit 466e6e9d13d56bbb6da1d2396d7d6347df483af0:
target-i386: reorder fields in cpu/msr_hyperv_hypercall subsection (2014-04-05 10:49:05 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-gtk-4
for you to fetch changes up to 25eccc37ff91254efdd123f5dafb37526a83a990:
ui: Update MAINTAINERS entry. (2014-04-07 10:50:30 +0200)
----------------------------------------------------------------
gtk: pointer fixes from Takashi Iwai.
----------------------------------------------------------------
Gerd Hoffmann (1):
ui: Update MAINTAINERS entry.
Takashi Iwai (3):
gtk: Use gtk generic event signal instead of motion-notify-event
gtk: Fix the relative pointer tracking mode
gtk: Remember the last grabbed pointer position
MAINTAINERS | 3 ++-
ui/gtk.c | 46 +++++++++++++++++++++++++++++++++-------------
2 files changed, 35 insertions(+), 14 deletions(-)
next reply other threads:[~2014-04-07 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 8:56 Gerd Hoffmann [this message]
2014-04-07 8:56 ` [Qemu-devel] [PULL 1/4] gtk: Use gtk generic event signal instead of motion-notify-event Gerd Hoffmann
2014-04-07 8:56 ` [Qemu-devel] [PULL 2/4] gtk: Fix the relative pointer tracking mode Gerd Hoffmann
2014-04-07 8:56 ` [Qemu-devel] [PULL 3/4] gtk: Remember the last grabbed pointer position Gerd Hoffmann
2014-04-07 8:56 ` [Qemu-devel] [PULL 4/4] ui: Update MAINTAINERS entry Gerd Hoffmann
2014-04-07 11:50 ` [Qemu-devel] [PULL for-2.0 0/4] gtk: pointer fixes 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=1396860980-7130-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).