From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=39925 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OYa7o-0004PH-Ca
	for qemu-devel@nongnu.org; Tue, 13 Jul 2010 03:41:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1OYa6o-0001zr-1d
	for qemu-devel@nongnu.org; Tue, 13 Jul 2010 03:40:55 -0400
Received: from mx1.redhat.com ([209.132.183.28]:63898)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1OYa6n-0001zk-PP
	for qemu-devel@nongnu.org; Tue, 13 Jul 2010 03:40:54 -0400
Message-ID: <4C3C1878.2060003@redhat.com>
Date: Tue, 13 Jul 2010 10:40:40 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: KVM Call agenda for July 13th
References: <m3eif8iw82.fsf@trasno.mitica> <4C3BED6C.20601@redhat.com>
	<4C3C0E5C.50902@aurel32.net>
In-Reply-To: <4C3C0E5C.50902@aurel32.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/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: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>, Juan Quintela <quintela@redhat.com>

On 07/13/2010 09:57 AM, Aurelien Jarno wrote:
> Avi Kivity a =E9crit :
>   =20
>> On 07/12/2010 05:57 PM, Juan Quintela wrote:
>>     =20
>>> Please send in any agenda items you are interested in covering.
>>>
>>>
>>>       =20
>> 0.12.n+1
>>
>>     =20
> I won't be at the KVM call, but I can work on that in the next days.
>
> Basically the stable tree already contains a lot of fixes and we can do
> a call for patches for this release. One week should be enough, so that
> we can have the release at the end of next week (a few technical days
> are needed in addition).
>   =20

Thanks.

I'd like to see more frequent stable releases, at least if the stable=20
branch contains fixes to user-reported bugs (or of course security or=20
data integrity fixes).

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