From: Chris Wright <chrisw@redhat.com>
To: "Justin M. Forbes" <jmforbes@linuxtx.org>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call minutes for Apr 27
Date: Tue, 27 Apr 2010 09:51:28 -0700 [thread overview]
Message-ID: <20100427165128.GH12848@x200.localdomain> (raw)
In-Reply-To: <20100427163252.GA20274@linuxtx.org>
* Justin M. Forbes (jmforbes@linuxtx.org) wrote:
> On Tue, Apr 27, 2010 at 09:11:00AM -0700, Chris Wright wrote:
> >
> > stable tree policy (push vs. pull and call for stable volunteers)
> > - historically pull based (cherry picking)
> > - doesn't scale wwell
> > - push based...submit patches directly to stable tree
> > - not just add "good for stable" in uptream patch submission
> > - looking for volunteers to manage stable tree
> > - Anthony volunteers!! (ok, not really)
>
> I will volunterr for this. I have a vested interest in the stable tree,
> as I track to it with Fedora as well.
Excellent, thanks Justin. Anthony can work out the details with you.
thanks,
-chris
prev parent reply other threads:[~2010-04-27 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 16:11 [Qemu-devel] KVM call minutes for Apr 27 Chris Wright
2010-04-27 16:32 ` [Qemu-devel] " Justin M. Forbes
2010-04-27 16:51 ` Chris Wright [this message]
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=20100427165128.GH12848@x200.localdomain \
--to=chrisw@redhat.com \
--cc=jmforbes@linuxtx.org \
--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).