All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 2/6] spice: client migration.
Date: Tue, 11 Jan 2011 14:37:07 +0100	[thread overview]
Message-ID: <4D2C5D03.2040900@redhat.com> (raw)
In-Reply-To: <1294747706-31382-3-git-send-email-kraxel@redhat.com>

On 01/11/11 13:08, Gerd Hoffmann wrote:
> Handle spice client migration, i.e. inform a spice client connected
> about the new host and connection parameters, so it can move over the
> connection automatically.

Oops, scratch that, old patch file still lying around and the new one 
got another name due to the updated title.  The other 2/6 patch is the 
one which is actually in the git tree.

sorry,
   Gerd

  reply	other threads:[~2011-01-11 13:37 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   ` Gerd Hoffmann [this message]
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 ` [Qemu-devel] Re: [PULL v2 0/6] spice patch queue Gerd Hoffmann

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=4D2C5D03.2040900@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.