From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call agenda for Feb 16
Date: Tue, 16 Feb 2010 08:45:32 -0600 [thread overview]
Message-ID: <4B7AAF8C.1050809@codemonkey.ws> (raw)
In-Reply-To: <694D9944-56F9-4F0A-82E9-514B6860EEC5@suse.de>
On 02/16/2010 04:36 AM, Alexander Graf wrote:
> On 16.02.2010, at 09:04, Chris Wright wrote:
>
>
>> Please send in any agenda items you are interested in covering.
>>
> Stable policies. How do we assure everything that belongs to -stable actually goes to -stable?
>
For the most part, I try to be proactive about evaluating patches I
commit for stable. Often times, my pushes to stable lag significantly
behind my pushes to master. That's because I try to do much more
significant testing for stable and I think most people don't actually
test the stable branch, they rely on stable releases.
That said, I'm always willing to take patches backported to stable
(tagged with [STABLE]). Pull requests are also welcome but please post
patches first.
Regards,
Anthony Liguori
> Alex--
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-02-16 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 8:04 [Qemu-devel] KVM call agenda for Feb 16 Chris Wright
2010-02-16 10:36 ` [Qemu-devel] " Alexander Graf
2010-02-16 14:45 ` Anthony Liguori [this message]
2010-02-16 14:47 ` Anthony Liguori
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=4B7AAF8C.1050809@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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).