From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M6xTB-0000Ie-U1
	for qemu-devel@nongnu.org; Wed, 20 May 2009 21:53:17 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M6xT9-0000I6-Rz
	for qemu-devel@nongnu.org; Wed, 20 May 2009 21:53:16 -0400
Received: from [199.232.76.173] (port=49025 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M6xT9-0000I3-OV
	for qemu-devel@nongnu.org; Wed, 20 May 2009 21:53:15 -0400
Received: from qw-out-1920.google.com ([74.125.92.148]:49966)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <gabriel.southern@gmail.com>) id 1M6xT9-000131-E7
	for qemu-devel@nongnu.org; Wed, 20 May 2009 21:53:15 -0400
Received: by qw-out-1920.google.com with SMTP id 4so491310qwk.4
	for <qemu-devel@nongnu.org>; Wed, 20 May 2009 18:53:14 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <4A146C19.8090203@codemonkey.ws>
References: <4A146C19.8090203@codemonkey.ws>
Date: Wed, 20 May 2009 18:53:14 -0700
Message-ID: <3c2bf46d0905201853i38836a84oabfeb121ddf039ef@mail.gmail.com>
Subject: Re: [Qemu-devel] QEMU 0.10.5 release tomorrow
From: Gabriel Southern <gabriel.southern@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
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.gnu.org/pipermail/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: Anthony Liguori <anthony@codemonkey.ws>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

There is a problem with qemu-system-sparc that causes a segmentation
fault.  I think the problem was traced to the
9d07d7579bcaf01e05c511c63d091ed2ac310091 "PCI network qdev conversion"
commit, but I have not seen a fix yet.  I'm not sure how to check the
tagged release (I did not see a tag for v0.10.5) so I don't know if
0.10.5 will have this problem or not.

-Gabriel

On Wed, May 20, 2009 at 1:46 PM, Anthony Liguori <anthony@codemonkey.ws> wr=
ote:
> I've tagged the repo and will pre-publish the tarball. =A0The plan is to =
post
> tomorrow officially after the mirrors have propagated.
>
> If anyone finds a regression though, we could post-pone if necessary so
> please test.
>
> Regards,
>
> Anthony Liguori
>
>
>