From: Greg KH <greg@kroah.com>
To: Willy Tarreau <w@1wt.eu>
Cc: tim.gardner@canonical.com, stable@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, Ben Hutchings <ben@decadent.org.uk>
Subject: Re: Latest kernel stable/longterm status
Date: Sat, 21 Jan 2012 08:47:06 -0500 [thread overview]
Message-ID: <20120121134706.GA21515@kroah.com> (raw)
In-Reply-To: <20120121133620.GA10602@1wt.eu>
On Sat, Jan 21, 2012 at 02:36:20PM +0100, Willy Tarreau wrote:
> Hi Greg,
>
> On Wed, Jan 11, 2012 at 12:52:12PM -0800, Greg KH wrote:
> > On Wed, Jan 11, 2012 at 09:37:07PM +0100, Tim Gardner wrote:
> > > On 01/11/2012 04:12 PM, Greg KH wrote:
> > > >
> > > >As I previously stated, in this email, I already have someone lined up
> > > >to maintain 2.6.32 after I am done with it, but I'm sure that person
> > > >would love it if you would send any needed patches to
> > > >stable@vger.kernel.org to help them out.
> > > >
> > > >greg k-h
> > >
> > > I'm happy to work with whomever. Your original email with "it might
> > > be picked up by someone else, but I'm not going to promise anything"
> > > didn't seem that definite.
> >
> > Sorry, I didn't want to put words in the mouth of someone else, but
> > given that Willy has done a great job with 2.4 and 2.6.16, I'm pretty
> > sure he will continue to do well with 2.6.32.
>
> Thanks for the nice comment :-) Please note that I did not work on
> 2.6.16, Adrian did, I only worked on .20 and .27.
Ah, you are right, sorry about that, too many different trees :)
But also note that Adrian didn't really follow the "stable rules", so I
don't count that as proper maintaining of that tree.
> Yes I'm still interested in taking over 2.6.32 when you give it up. I
> must admit I've got quite silent last months, slowly trying to find time
> to backport 2.6.32 fixes into .27, and still a bit afraid by the added
> complexity of the new publication model. Time will tell. This weel-end
> I hope to be able to produce 2.6.27.60-rc1.
>
> What is very important to me is that I want people to complain if they
> find that I'm too slow, as I don't want to degrade the quality of the
> stable series by taking a position someone would take better.
I don't think you will do a bad job at all, You'll do fine, if you need
any help, feel free to ask.
thanks,
greg k-h
next prev parent reply other threads:[~2012-01-21 13:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 0:37 Latest kernel stable/longterm status Greg KH
2012-01-10 2:26 ` Steven Rostedt
2012-01-10 10:03 ` Tim Gardner
2012-01-10 23:56 ` Greg KH
2012-01-11 1:38 ` Anca Emanuel
2012-01-11 10:10 ` Tim Gardner
2012-01-11 15:12 ` Greg KH
2012-01-11 20:37 ` Tim Gardner
2012-01-11 20:52 ` Greg KH
2012-01-21 13:36 ` Willy Tarreau
2012-01-21 13:47 ` Greg KH [this message]
2012-01-21 14:45 ` Willy Tarreau
2012-01-11 12:32 ` Geert Uytterhoeven
2012-01-11 12:42 ` Geert Uytterhoeven
2012-01-11 15:13 ` Greg KH
2012-01-11 15:13 ` Greg KH
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=20120121134706.GA21515@kroah.com \
--to=greg@kroah.com \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=tim.gardner@canonical.com \
--cc=w@1wt.eu \
/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.