All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: 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: 3.12-stable kernel tree being taken over by Jiri Slaby
Date: Wed, 26 Feb 2014 15:19:10 -0800	[thread overview]
Message-ID: <20140226231910.GA8789@kroah.com> (raw)

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.

The kernel.org page has already been updated with this information:
	https://www.kernel.org/category/releases.html

If anyone has any questions about this, please let me know.

David, I don't know if you want to keep doing 3.12-networking patches or
not, I'll let you work that out with Jiri directly.

thanks,

greg k-h

             reply	other threads:[~2014-02-26 23:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 23:19 Greg Kroah-Hartman [this message]
2014-02-26 23:39 ` 3.12-stable kernel tree being taken over by Jiri Slaby 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
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=20140226231910.GA8789@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --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 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.