From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LgGuP-0008IF-My
	for qemu-devel@nongnu.org; Sun, 08 Mar 2009 07:11:05 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LgGuM-0008Hf-2k
	for qemu-devel@nongnu.org; Sun, 08 Mar 2009 07:11:05 -0400
Received: from [199.232.76.173] (port=36094 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LgGuL-0008HY-Uk
	for qemu-devel@nongnu.org; Sun, 08 Mar 2009 07:11:01 -0400
Received: from mx2.redhat.com ([66.187.237.31]:50224)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1LgGuL-0005ap-I0
	for qemu-devel@nongnu.org; Sun, 08 Mar 2009 07:11:01 -0400
Message-ID: <49B3A7C1.2090707@redhat.com>
Date: Sun, 08 Mar 2009 13:10:57 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] ANNOUNCE: QEMU 0.10.0 stable branch
References: <49B01FFD.7040900@codemonkey.ws>
In-Reply-To: <49B01FFD.7040900@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: qemu-devel@nongnu.org
Cc: kvm-devel <kvm@vger.kernel.org>

Anthony Liguori wrote:
> Hi,
>
> I'd like to announce the creation of a QEMU stable branch based on the 
> recent 0.10.0 release.  You can access it via anonymous SVN via:
>
>  svn co svn://svn.savannah.nongnu.org/qemu/branches/stable_0_10_0
>
> The stable branch will receive bug fixes from trunk until at least the 
> next major release.  If submitting a bug fix, please consider also 
> testing the patch against stable and sending multiple patches if 
> appropriate.  Using a tag in the subject line like [STABLE] would also 
> be helpful to indicate to the maintainers that a patch should be 
> considered for the stable tree.
>
> As the stable tree accumulates fixes, we'll make new stable releases 
> from the tree.
>

Will a stable release be called 0.10.0.1 or 0.10.1? (I'd prefer the latter)

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