From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:46086) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ra89f-0006cB-HR for qemu-devel@nongnu.org; Mon, 12 Dec 2011 10:51:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ra89Z-0007VB-4d for qemu-devel@nongnu.org; Mon, 12 Dec 2011 10:51:03 -0500 Received: from mx1.redhat.com ([209.132.183.28]:61937) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ra89Y-0007V6-U0 for qemu-devel@nongnu.org; Mon, 12 Dec 2011 10:50:57 -0500 Date: Mon, 12 Dec 2011 17:50:46 +0200 From: Alon Levy Message-ID: <20111212155046.GB29447@garlic.tlv.redhat.com> References: <20111208174544.325838a6@doriath> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111208174544.325838a6@doriath> Subject: Re: [Qemu-devel] Dropping the MONITOR_CMD_ASYNC List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: kraxel@redhat.com, qemu-devel , stefanha@linux.vnet.ibm.com 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? > 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? :) >