From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 0/3] Ui 20180202 patches
Date: Fri, 2 Feb 2018 08:17:48 +0100 [thread overview]
Message-ID: <20180202071751.16316-1-kraxel@redhat.com> (raw)
The following changes since commit 11ed801d3df3c6e46b2f1f97dcfbf4ca3a2a2f4f:
Merge remote-tracking branch 'remotes/stefanha/tags/tracing-pull-request' into staging (2018-01-30 09:47:51 +0000)
are available in the git repository at:
git://git.kraxel.org/qemu tags/ui-20180202-pull-request
for you to fetch changes up to 627ebec208a8809818589e17f4fce55a59420ad2:
ui: correctly advance output buffer when writing SASL data (2018-02-02 07:48:18 +0100)
----------------------------------------------------------------
ui: use QIONetListener in vnc, bugfixes for sdl1 and vnc.
----------------------------------------------------------------
Daniel P. Berrange (1):
ui: convert VNC server to QIONetListener
Daniel P. Berrangé (2):
ui: fix mixup between qnum and qcode in SDL1 key handling
ui: correctly advance output buffer when writing SASL data
ui/vnc.h | 9 +--
ui/sdl.c | 9 ++-
ui/vnc-auth-sasl.c | 2 +-
ui/vnc.c | 195 +++++++++++++++--------------------------------------
4 files changed, 67 insertions(+), 148 deletions(-)
--
2.9.3
next reply other threads:[~2018-02-02 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 7:17 Gerd Hoffmann [this message]
2018-02-02 7:17 ` [Qemu-devel] [PULL 1/3] ui: fix mixup between qnum and qcode in SDL1 key handling Gerd Hoffmann
2018-02-02 7:17 ` [Qemu-devel] [PULL 2/3] ui: convert VNC server to QIONetListener Gerd Hoffmann
2018-02-02 7:17 ` [Qemu-devel] [PULL 3/3] ui: correctly advance output buffer when writing SASL data Gerd Hoffmann
2018-02-02 17:49 ` [Qemu-devel] [PULL 0/3] Ui 20180202 patches Eric Blake
2018-02-02 18:29 ` Daniel P. Berrangé
2018-02-05 9:31 ` 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=20180202071751.16316-1-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).