From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Mh3Vp-00064F-OA
	for qemu-devel@nongnu.org; Fri, 28 Aug 2009 11:37:13 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Mh3Vl-00060M-Sh
	for qemu-devel@nongnu.org; Fri, 28 Aug 2009 11:37:13 -0400
Received: from [199.232.76.173] (port=54721 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Mh3Vl-00060G-Lt
	for qemu-devel@nongnu.org; Fri, 28 Aug 2009 11:37:09 -0400
Received: from qw-out-1920.google.com ([74.125.92.145]:60453)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1Mh3Vl-0007Up-Ao
	for qemu-devel@nongnu.org; Fri, 28 Aug 2009 11:37:09 -0400
Received: by qw-out-1920.google.com with SMTP id 5so463507qwc.4
	for <qemu-devel@nongnu.org>; Fri, 28 Aug 2009 08:37:07 -0700 (PDT)
Message-ID: <4A97F9A1.6030206@codemonkey.ws>
Date: Fri, 28 Aug 2009 10:37:05 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
References: <200908280220.n7S2JlNq027935@d03av04.boulder.ibm.com>
	<200908281005.20817.rickv@hobi.com>
In-Reply-To: <200908281005.20817.rickv@hobi.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [Qemu-commits] [COMMIT f3566bf] cirrus_vga: Change
 casts to DO_UPCAST() forPCICirrusVGAState
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: Rick Vernam <rickv@hobi.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

Rick Vernam wrote:
> I apologize for my apparent ignorance.
> I am curious how one ascertains from a commit message such as this where the 
> patch was applied?  ie, only to the 0.12 branch...or?
>
> In particular, I will be sticking with the 0.11 branch until I get hardware 
> with virtualization support.  How can I tell which commits are applied to that 
> branch?
>   

The commit list is just for the master branch which is the 0.12 
development tree.

All patches that go in one of the stable branches tend to go through 
master first.  We could setup additional hooks for the other branches 
but so far, there hasn't been much demand.

N.B. only bug fixes will go into any of the stable branches.  No new 
features will be added to these branches.

Regards,

Anthony Liguori

>