From: Anthony Liguori <anthony@codemonkey.ws>
To: Rick Vernam <rickv@hobi.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [Qemu-commits] [COMMIT f3566bf] cirrus_vga: Change casts to DO_UPCAST() forPCICirrusVGAState
Date: Fri, 28 Aug 2009 10:37:05 -0500 [thread overview]
Message-ID: <4A97F9A1.6030206@codemonkey.ws> (raw)
In-Reply-To: <200908281005.20817.rickv@hobi.com>
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
>
parent reply other threads:[~2009-08-28 15:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200908281005.20817.rickv@hobi.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A97F9A1.6030206@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=rickv@hobi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).