From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 0/3] vnc: misc bugfixes
Date: Tue, 12 Jul 2016 09:23:40 +0200 [thread overview]
Message-ID: <1468308223-2496-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
A collection of vnc bugfixes from the last weeks.
please pull,
Gerd
The following changes since commit f1ef55786691a1bf79db0b74ba1e5347a0d38c1b:
Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20160711' into staging (2016-07-11 18:46:38 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-vnc-20160712-1
for you to fetch changes up to ea697449884d83b83fefbc9cd87bdde0c94b49d6:
ui: avoid crash if vnc client disconnects with writes pending (2016-07-12 08:34:13 +0200)
----------------------------------------------------------------
vnc: misc bugfixes.
----------------------------------------------------------------
Daniel P. Berrange (1):
ui: avoid crash if vnc client disconnects with writes pending
Gonglei (1):
vnc: fix incorrect checking condition when updating client
Peter Lieven (1):
vnc-enc-tight: use thread local storage for palette
ui/vnc-enc-tight.c | 23 ++++++++++++-----------
ui/vnc.c | 15 ++++++++++-----
2 files changed, 22 insertions(+), 16 deletions(-)
next reply other threads:[~2016-07-12 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 7:23 Gerd Hoffmann [this message]
2016-07-12 7:23 ` [Qemu-devel] [PULL 1/3] vnc: fix incorrect checking condition when updating client Gerd Hoffmann
2016-07-12 7:23 ` [Qemu-devel] [PULL 2/3] vnc-enc-tight: use thread local storage for palette Gerd Hoffmann
2016-07-12 7:23 ` [Qemu-devel] [PULL 3/3] ui: avoid crash if vnc client disconnects with writes pending Gerd Hoffmann
2016-07-12 9:58 ` [Qemu-devel] [PULL 0/3] vnc: misc bugfixes 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=1468308223-2496-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).