From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
Jiri Slaby <jslaby@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, David Miller <davem@davemloft.net>
Subject: Re: 3.12-stable kernel tree being taken over by Jiri Slaby
Date: Thu, 27 Feb 2014 19:02:04 -0800 [thread overview]
Message-ID: <530FFC2C.5010305@roeck-us.net> (raw)
In-Reply-To: <20140226231910.GA8789@kroah.com>
On 02/26/2014 03:19 PM, Greg Kroah-Hartman wrote:
> As I hinted at in my kernel summit talk about the stable kernel tree, we
> have a sucker^Wvolunteer who has stepped up to take over the longterm
> maintenance of the 3.12 stable kernel tree.
>
> Jiri Slaby will be doing this work, for how ever long he wants to do it.
> I'll still be doing the final releases to kernel.org, like I do for 3.2,
> but Jiri will be doing the collecting of patches and other real work
> involved in it, including the announcements for its release.
>
Jiri,
do you want me to keep running my build tests on the patch queue for 3.12 ?
If yes, I'll probably need to know the location of your (quilt ?) repository
so I can import the patches, similar to what I do for 3.2 and the releases
managed by Greg.
Thanks,
Guenter
next prev parent reply other threads:[~2014-02-28 3:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 23:19 3.12-stable kernel tree being taken over by Jiri Slaby Greg Kroah-Hartman
2014-02-26 23:39 ` David Miller
2014-02-27 8:42 ` Jiri Slaby
2014-02-27 8:51 ` Jiri Slaby
2014-02-27 17:55 ` David Miller
2014-02-28 3:02 ` Guenter Roeck [this message]
2014-03-01 9:28 ` Jiri Slaby
2014-03-01 19:05 ` Guenter Roeck
2014-02-28 15:58 ` Shuah Khan
2014-03-01 19:53 ` Jiri Slaby
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=530FFC2C.5010305@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).