From: "Justin M. Forbes" <jmforbes@linuxtx.org>
To: Brad <brad@comstyle.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-0.15.1 stable call for patches
Date: Wed, 12 Oct 2011 11:34:26 -0500 [thread overview]
Message-ID: <1318437267.27683.36.camel@fedora64.linuxtx.org> (raw)
In-Reply-To: <4E9560C5.2090205@comstyle.com>
On Wed, 2011-10-12 at 05:41 -0400, Brad wrote:
> On 26/09/11 9:16 AM, Justin M. Forbes wrote:
> > With the current patch queue I would like to start getting qemu-0.15.1
> > stable into shape. With this in mind, the plan is to tag the release on
> > Monday Oct 3rd. If you have patches pending for stable, now would be the
> > time to send them. Please CC jmforbes@linuxtx.org if you can to ensure that
> > I see them.
> >
> > Thanks,
> > Justin
>
> Is there anywhere where we can see what's been pulled into the pending
> 0.15.1 code base so far since you don't seem to really post to the list
> about the stable branches?
>
I typically reply when things get applied, though you can always check
the git tree at:
git://git.qemu.org/qemu-stable-0.15.git
Justin
prev parent reply other threads:[~2011-10-12 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 13:16 [Qemu-devel] qemu-0.15.1 stable call for patches Justin M. Forbes
2011-10-12 9:41 ` Brad
2011-10-12 16:34 ` Justin M. Forbes [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=1318437267.27683.36.camel@fedora64.linuxtx.org \
--to=jmforbes@linuxtx.org \
--cc=brad@comstyle.com \
--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).