From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKDfO-0002tT-Ng for qemu-devel@nongnu.org; Mon, 14 Dec 2009 11:20:58 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKDfK-0002oX-G5 for qemu-devel@nongnu.org; Mon, 14 Dec 2009 11:20:58 -0500 Received: from [199.232.76.173] (port=38958 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKDfK-0002oP-7r for qemu-devel@nongnu.org; Mon, 14 Dec 2009 11:20:54 -0500 Received: from e3.ny.us.ibm.com ([32.97.182.143]:60376) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NKDfK-0001HT-2M for qemu-devel@nongnu.org; Mon, 14 Dec 2009 11:20:54 -0500 Received: from d01relay05.pok.ibm.com (d01relay05.pok.ibm.com [9.56.227.237]) by e3.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id nBEGBfOV008268 for ; Mon, 14 Dec 2009 11:11:41 -0500 Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay05.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id nBEGKq2u129632 for ; Mon, 14 Dec 2009 11:20:53 -0500 Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id nBEGKqMH031918 for ; Mon, 14 Dec 2009 14:20:52 -0200 Message-ID: <4B2665E2.9070603@linux.vnet.ibm.com> Date: Mon, 14 Dec 2009 10:20:50 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [ANNOUNCE][Call-For-Testing] Release 0.12.0-rc1 of QEMU References: <4B264659.80201@linux.vnet.ibm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Artyom Tarasenko Cc: Blue Swirl , "qemu-devel@nongnu.org" Artyom Tarasenko wrote: > 2009/12/14 Anthony Liguori : > >> The current plan is to release 0.12.0 on Friday, Dec 18th. Depending on the >> severity of bug fixes we get between now and then, we may do another release >> candidate in the middle of the week. >> > > I see that the carry flag fix for sparc is included. Are you planning > to include the rest of my sparc/scsi patches? They are not as drastic > as the carry fix, so they shouldn't break something which isn't > already broken. On the other hand, the ability to boot Solaris/sparc > kernel may be important for some users. > It's up to Blue Swirl to decide about the sparc patches. The SCSI Inquiry fix is reasonable but it missed the -rc2 deadline. I'll queue it for final release. -- Regards, Anthony Liguori