From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:33637) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RYjuh-0004e1-Iq for qemu-devel@nongnu.org; Thu, 08 Dec 2011 14:45:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RYjug-0007OM-EU for qemu-devel@nongnu.org; Thu, 08 Dec 2011 14:45:51 -0500 Received: from mx1.redhat.com ([209.132.183.28]:64421) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RYjug-0007OI-6h for qemu-devel@nongnu.org; Thu, 08 Dec 2011 14:45:50 -0500 Date: Thu, 8 Dec 2011 17:45:44 -0200 From: Luiz Capitulino Message-ID: <20111208174544.325838a6@doriath> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Dropping the MONITOR_CMD_ASYNC List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel Cc: alevy@redhat.com, stefanha@linux.vnet.ibm.com, kraxel@redhat.com 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... 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? :)