From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LgKyv-0002Ht-R5 for qemu-devel@nongnu.org; Sun, 08 Mar 2009 11:32:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LgKys-00029C-LX for qemu-devel@nongnu.org; Sun, 08 Mar 2009 11:32:01 -0400 Received: from [199.232.76.173] (port=34906 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LgKys-00028x-8p for qemu-devel@nongnu.org; Sun, 08 Mar 2009 11:31:58 -0400 Received: from mx2.redhat.com ([66.187.237.31]:39531) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LgKyr-0003R3-Pj for qemu-devel@nongnu.org; Sun, 08 Mar 2009 11:31:58 -0400 Message-ID: <49B3E4E8.9080700@redhat.com> Date: Sun, 08 Mar 2009 17:31:52 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] ANNOUNCE: QEMU 0.10.0 stable branch References: <49B01FFD.7040900@codemonkey.ws> <49B3A7C1.2090707@redhat.com> <49B3E29F.1080400@codemonkey.ws> In-Reply-To: <49B3E29F.1080400@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: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: kvm-devel Anthony Liguori wrote: > Avi Kivity wrote: >> 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) > > I was thinking the later but am open to suggestion. In this case, the branch ought to be called stable_0_10, no? -- error compiling committee.c: too many arguments to function