From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=47618 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PpLZ1-0000ic-VY for qemu-devel@nongnu.org; Tue, 15 Feb 2011 09:07:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PpLZ0-0002KI-Qo for qemu-devel@nongnu.org; Tue, 15 Feb 2011 09:07:35 -0500 Received: from mx1.redhat.com ([209.132.183.28]:53576) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PpLZ0-0002K8-Hu for qemu-devel@nongnu.org; Tue, 15 Feb 2011 09:07:34 -0500 From: Markus Armbruster Subject: What's QAPI? (was: [Qemu-devel] [RFC] qapi: events in QMP) References: <4D581E04.1020901@codemonkey.ws> Date: Tue, 15 Feb 2011 15:07:21 +0100 In-Reply-To: <4D581E04.1020901@codemonkey.ws> (Anthony Liguori's message of "Sun, 13 Feb 2011 12:08:04 -0600") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Kevin Wolf , qemu-devel , Luiz Capitulino Anthony Liguori writes: > Hi, > > In my QAPI branch[1], I've now got almost every existing QMP command > converted with (hopefully) all of the hard problems solved. There is > only one remaining thing to attack before posting for inclusion and > that's events. Here's my current thinking about what to do. Have you put your thinking behind the QAPI branch in writing anywhere? Ideally in comparable detail as your discussion of events in QAPI (which I snipped). [...]