From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:58445)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1RsEP7-0000H5-AA
	for qemu-devel@nongnu.org; Tue, 31 Jan 2012 09:09:54 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1RsEOy-0004kx-IU
	for qemu-devel@nongnu.org; Tue, 31 Jan 2012 09:09:49 -0500
Received: from mx1.redhat.com ([209.132.183.28]:12502)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1RsEOy-0004kl-9B
	for qemu-devel@nongnu.org; Tue, 31 Jan 2012 09:09:40 -0500
Message-ID: <4F27F61B.6040806@redhat.com>
Date: Tue, 31 Jan 2012 16:09:31 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <87ehuhrpel.fsf@elfo.elfo> <4F272A92.2010609@suse.de>
	<4F27F3DB.2040400@codemonkey.ws>
In-Reply-To: <4F27F3DB.2040400@codemonkey.ws>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] KVM call agenda for tuesday 31
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Peter Maydell <peter.maydell@linaro.org>, KVM devel mailing list <kvm@vger.kernel.org>, =?UTF-8?B?6Zmz6Z+L5Lu7?= <chenwj@iis.sinica.edu.tw>, quintela@redhat.com, Stefan Weil <sw@weilnetz.de>, Developers qemu-devel <qemu-devel@nongnu.org>, =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= <afaerber@suse.de>, Alex Bradbury <asb@asbradbury.org>

On 01/31/2012 03:59 PM, Anthony Liguori wrote:
> On 01/30/2012 05:41 PM, Andreas F=C3=A4rber wrote:
>> Am 30.01.2012 19:55, schrieb Juan Quintela:
>>> Please send in any agenda items you are interested in covering.
>>
>> QOM roadmap update:
>> * Series 3/4 is on the list.
>> ->  Please officially designate a merge date (Friday?).
>> ->  To make review sensible, I ask for a hard device freeze until
>> merged.
>>     I.e., no new devices and no conflicting changes to DeviceInfo.
>
> I put together a few slides to help this discussion:
>
> http://www.codemonkey.ws/files/qom-overview.pdf
>

That was helpful, thanks.

Can you clarify

- Types and their properties will be ABI  compatible
- Types and properties will not be backwards  compatible
=E2=80=93 We can re-examine this as the device model  matures and stabili=
zes

the first two seem very similar, except for the "not".


--=20
error compiling committee.c: too many arguments to function