From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KsINd-0004qP-HH
	for qemu-devel@nongnu.org; Tue, 21 Oct 2008 10:38:41 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KsINb-0004pY-Vt
	for qemu-devel@nongnu.org; Tue, 21 Oct 2008 10:38:41 -0400
Received: from [199.232.76.173] (port=39774 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KsINb-0004pL-Ob
	for qemu-devel@nongnu.org; Tue, 21 Oct 2008 10:38:39 -0400
Received: from relay01.mx.bawue.net ([193.7.176.67]:44636)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <ths@networkno.de>) id 1KsINb-0000pW-AM
	for qemu-devel@nongnu.org; Tue, 21 Oct 2008 10:38:39 -0400
Date: Tue, 21 Oct 2008 16:38:34 +0200
From: Thiemo Seufer <ths@networkno.de>
Subject: Re: [Qemu-devel] release date of qemu 0.9.2?
Message-ID: <20081021143834.GA29344@networkno.de>
References: <BAY110-DAV368495AFEC122115C5BA7B92E0@phx.gbl>
	<48FDD9DD.4010906@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48FDD9DD.4010906@codemonkey.ws>
Reply-To: qemu-devel@nongnu.org
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

Anthony Liguori wrote:
> C.W. Betts wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> When will qemu be given the status of 0.9.2?  I was browsing the  
>> source code of the Qemu that ships with OpenSuSE and noticed that  
>> there are a lot of patches.  It would probably be helpful if there was  
>> a release that didn't depend on GCC 4.
>>
>> Also, what targets still depend on dyngen?  And is anyone working on  
>> porting them to TCG?
>
> A lot of previously supported hosts are no longer supported with TCG.  I  
> would think adding those hosts would be more important than completing  
> the TCG conversion before cutting a new release.

I disagree. The most important hosts are supported, the other hosts
were largely experimental anyway, and getting rid of dyngen / gcc3
is IMHO worth a release.


Thiemo