From: Keir Fraser <keir@xen.org>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Time for 4.2.0 rc0?
Date: Mon, 30 Jul 2012 16:17:57 +0100 [thread overview]
Message-ID: <CC3C6435.471CC%keir@xen.org> (raw)
In-Reply-To: <1343661164.15432.32.camel@zakaz.uk.xensource.com>
On 30/07/2012 16:12, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:
> On Mon, 2012-07-30 at 16:09 +0100, Ian Jackson wrote:
>> Keir Fraser writes ("Re: [Xen-devel] Time for 4.2.0 rc0?"):
>>> On 30/07/2012 15:52, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:
>>>> Possibly the blktap2 ones too, but they are pretty internal I guess.
>>>
>>> Do you want to do these now?
>>
>> This should be done by a patch posted to the list really. We can
>> either post and apply it, or we can do the RC without it and bump the
>> patch numbers later.
>
> Lets go ahead with RC1. I'll add this to the TODO list as something to
> be done before release (ideally earlier rather than later in the RC
> cycle)
Okay, done. And I also pushed version update to 4.2.0-rc2-pre to tip,
proactively. ;)
-- Keir
> Ian.
>
next prev parent reply other threads:[~2012-07-30 15:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 10:09 Time for 4.2.0 rc0? Ian Campbell
2012-07-27 10:34 ` Keir Fraser
2012-07-27 10:54 ` Ian Campbell
2012-07-30 8:26 ` Ian Campbell
2012-07-30 12:28 ` Keir Fraser
2012-07-30 12:37 ` Ian Campbell
2012-07-30 12:41 ` Keir Fraser
2012-07-30 14:28 ` Ian Jackson
2012-07-30 14:42 ` Ian Jackson
2012-07-30 14:52 ` Ian Campbell
2012-07-30 14:56 ` Ian Jackson
2012-07-30 15:02 ` Ian Campbell
2012-07-30 15:05 ` Keir Fraser
2012-07-30 15:09 ` Ian Jackson
2012-07-30 15:12 ` Ian Campbell
2012-07-30 15:17 ` Keir Fraser [this message]
2012-07-30 15:20 ` Jan Beulich
2012-07-30 15:27 ` Ian Campbell
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=CC3C6435.471CC%keir@xen.org \
--to=keir@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.