From: Luiz Capitulino <lcapitulino@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: kraxel@redhat.com, qemu-devel <qemu-devel@nongnu.org>,
stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] Dropping the MONITOR_CMD_ASYNC
Date: Mon, 12 Dec 2011 14:08:00 -0200 [thread overview]
Message-ID: <20111212140800.11873fa8@doriath> (raw)
In-Reply-To: <20111212155046.GB29447@garlic.tlv.redhat.com>
On Mon, 12 Dec 2011 17:50:46 +0200
Alon Levy <alevy@redhat.com> wrote:
> On Thu, Dec 08, 2011 at 05:45:44PM -0200, Luiz Capitulino wrote:
> > Hi there,
> >
> > I'm about to completely drop the MONITOR_CMD_ASYNC API, but it turns out that
> > the command client_migrate_info uses it. That's a legacy interface and has to
> > be dropped, no command should be using it...
> >
>
> Why has it got to be dropped? can't it be declared as deprecated first?
Well, after this thread looks like it's what we'll have to do...
>
> > Something tells me that if I just drop it (and change the command to use the
> > regular interface), bad things will happen. Am I right? :)
> >
>
next prev parent reply other threads:[~2011-12-12 16:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 19:45 [Qemu-devel] Dropping the MONITOR_CMD_ASYNC Luiz Capitulino
2011-12-11 10:29 ` Alon Levy
2011-12-12 10:18 ` Stefan Hajnoczi
2011-12-12 11:29 ` Gerd Hoffmann
2011-12-12 12:10 ` Stefan Hajnoczi
2011-12-12 12:39 ` Gerd Hoffmann
2011-12-12 15:23 ` Stefan Hajnoczi
2011-12-12 16:00 ` Alon Levy
2011-12-12 16:24 ` Anthony Liguori
2011-12-12 17:22 ` Alon Levy
2011-12-12 17:53 ` Anthony Liguori
2011-12-13 9:03 ` Alon Levy
2011-12-13 13:34 ` Anthony Liguori
2011-12-13 10:06 ` Gerd Hoffmann
2011-12-12 16:23 ` Anthony Liguori
2011-12-12 15:50 ` Alon Levy
2011-12-12 16:08 ` Luiz Capitulino [this message]
2011-12-12 16:26 ` Anthony Liguori
2011-12-13 11:06 ` Avi Kivity
2011-12-13 13:36 ` Anthony Liguori
2011-12-13 14:47 ` Avi Kivity
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=20111212140800.11873fa8@doriath \
--to=lcapitulino@redhat.com \
--cc=alevy@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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.