From: Gerd Hoffmann <kraxel@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PULL v2 0/6] spice patch queue
Date: Wed, 12 Jan 2011 11:07:07 +0100 [thread overview]
Message-ID: <4D2D7D4B.2050300@redhat.com> (raw)
In-Reply-To: <1294747706-31382-1-git-send-email-kraxel@redhat.com>
On 01/11/11 13:08, Gerd Hoffmann wrote:
> Hi,
>
> Here is a bunch of spice patches accumuled this year,
> they all have been on the list for review.
>
> [ v2: rewrite the spice client migration in a way that
> allows vnc to easily join the party later on ]
>
> please pull,
> Gerd
Looks like anthony wants to have some broader discussion on the agent
and spice chardev stuff, also blue swirl had some review comments on the
chardev stuff.
> are available in the git repository at:
> git://anongit.freedesktop.org/spice/qemu spice.v28.pull
Created a spice.v28.pull2 branch which just excludes patch 6/6 (the
chardev one), so the chardev discussions don't hold up the merging of
the other spice bits.
cheers,
Gerd
prev parent reply other threads:[~2011-01-12 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 12:08 [Qemu-devel] [PULL v2 0/6] spice patch queue Gerd Hoffmann
2011-01-11 12:08 ` [Qemu-devel] [PATCH 1/6] add migration state change notifiers Gerd Hoffmann
2011-01-11 12:08 ` [Qemu-devel] [PATCH 2/6] spice: client migration Gerd Hoffmann
2011-01-11 13:37 ` [Qemu-devel] " Gerd Hoffmann
2011-01-11 12:08 ` [Qemu-devel] [PATCH 2/6] spice/vnc: " Gerd Hoffmann
2011-01-11 12:08 ` [Qemu-devel] [PATCH 3/6] spice: MAINTAINERS update Gerd Hoffmann
2011-01-11 12:08 ` [Qemu-devel] [PATCH 4/6] vnc/spice: fix "never" and "now" expire_time Gerd Hoffmann
2011-01-11 12:08 ` [Qemu-devel] [PATCH 5/6] spice/qxl: zap spice 0.4 migration compatibility bits Gerd Hoffmann
2011-01-11 12:08 ` [Qemu-devel] [PATCH 6/6] spice: add chardev (v4) Gerd Hoffmann
2011-01-11 17:08 ` Blue Swirl
2011-01-12 10:07 ` Gerd Hoffmann [this message]
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=4D2D7D4B.2050300@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).