qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 0/6] ui patch queue.
Date: Fri, 28 Oct 2016 14:11:32 +0200	[thread overview]
Message-ID: <1477656698-13569-1-git-send-email-kraxel@redhat.com> (raw)

  Hi,

Here comes the UI patch queue with bugfixes for gtk and curses UIs and
the baum braille support.

I've cherry-picked from Samuel's patches the ones which are ready to
merge.  There is more in the pipeline for better unicode support in
curses, but those will probably not make the 2.8 freeze deadline.

please pull,
  Gerd

The following changes since commit db4df20de86c6e8ecd6c9f042c029ffb9f9cddac:

  trace: Fix 'char **' compilation error in simple backend (2016-10-27 19:24:15 +0100)

are available in the git repository at:

  git://git.kraxel.org/qemu tags/pull-ui-20161028-1

for you to fetch changes up to 8ddc5bf9e5de51c2a4842c01dd3a97f5591776fd:

  curses: Use cursesw instead of curses (2016-10-28 11:19:38 +0200)

----------------------------------------------------------------
braille fixes and improvements.
curses fix, switch to cursesw.
gtk bugfixes.

----------------------------------------------------------------
Alberto Garcia (1):
      gtk: fix compilation warning with gtk 3.22.2

Samuel Thibault (4):
      Add dots keypresses support to the baum braille device
      Defer BrlAPI tty acquisition to when guest starts using device
      curses: fix left/right arrow translation
      curses: Use cursesw instead of curses

Thomas Huth (1):
      ui/gtk: Fix non-working DELETE key

 backends/baum.c | 305 ++++++++++++++++++++++++++++++++------------------------
 configure       |  29 ++++--
 ui/curses.c     |   4 +-
 ui/gtk.c        |  27 ++++-
 4 files changed, 220 insertions(+), 145 deletions(-)

             reply	other threads:[~2016-10-28 12:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 12:11 Gerd Hoffmann [this message]
2016-10-28 12:11 ` [Qemu-devel] [PULL 1/6] Add dots keypresses support to the baum braille device Gerd Hoffmann
2016-10-28 12:11 ` [Qemu-devel] [PULL 2/6] Defer BrlAPI tty acquisition to when guest starts using device Gerd Hoffmann
2016-10-28 12:11 ` [Qemu-devel] [PULL 3/6] gtk: fix compilation warning with gtk 3.22.2 Gerd Hoffmann
2016-10-28 12:11 ` [Qemu-devel] [PULL 4/6] ui/gtk: Fix non-working DELETE key Gerd Hoffmann
2016-10-28 12:11 ` [Qemu-devel] [PULL 5/6] curses: fix left/right arrow translation Gerd Hoffmann
2016-10-28 12:11 ` [Qemu-devel] [PULL 6/6] curses: Use cursesw instead of curses Gerd Hoffmann
2016-10-31 11:45   ` Cornelia Huck
2016-10-31 12:01     ` Samuel Thibault
2016-10-31 12:05       ` Samuel Thibault
2016-10-31 12:08       ` Cornelia Huck
2016-10-31 12:16         ` Samuel Thibault
2016-10-31 12:39         ` Samuel Thibault
2016-10-31 12:48           ` Cornelia Huck
2016-10-31 14:03             ` Samuel Thibault
2016-10-31 13:08               ` Cornelia Huck
2016-10-31 15:39                 ` Samuel Thibault
2016-11-02  9:09                   ` Cornelia Huck
2016-10-28 17:55 ` [Qemu-devel] [PULL 0/6] ui patch queue Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2015-11-03 10:01 Gerd Hoffmann
2015-11-03 11:17 ` 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=1477656698-13569-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).