From: Willy Tarreau <w@1wt.eu>
To: Greg KH <greg@kroah.com>
Cc: Adrian Bunk <bunk@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable@kernel.org
Subject: Re: [stable] Linux 2.6.27 will be a longtime supported kernel
Date: Sun, 12 Oct 2008 09:00:45 +0200 [thread overview]
Message-ID: <20081012070044.GM24654@1wt.eu> (raw)
In-Reply-To: <20081012040223.GC18221@kroah.com>
On Sat, Oct 11, 2008 at 09:02:23PM -0700, Greg KH wrote:
> On Sun, Oct 12, 2008 at 12:03:40AM +0300, Adrian Bunk wrote:
> > 2.6.16 has become a bit dated, and I'll maintain 2.6.27 for a few years
> > as a replacement.
>
> Hm, you're not the only one going to be doing this, there are at least
> three distros basing their latest releases on this kernel :)
Oh that's good news as it will give it more exposure and bugs will be
found and fixed faster. Having 2.6.25 in opensuse may have contributed
to its stability.
> > As with 2.6.16, I'll pickup maintainance when the normal -stable
> > maintainance ends (at some point after 2.6.28 gets released in January).
>
> I was considering hanging on to .27 for a while longer than the .28
> release, much like .25 has been working out.
BTW, how long to you think you'll keep pushing fixes for .25 ? It's been
working really well and might have been the most reliable 2.6 I've seen,
2.6.16 aside. I'll keep using it waiting for 2.6.27 to settle down a bit.
> Hey, I personally liked it as it made maintaining SLES a lot easier,
> thanks a lot for your work there!
Not only there, but everywhere you need to embed a 2.6 without too many
features and without an easy ability to upgrade it, 2.6.16 has been a
good choice.
Thanks to you guys for the time you spend maintaining stable releases!
I really hope that 2.6.27 will be a viable replacement for 2.4 in the
long term.
Willy
next prev parent reply other threads:[~2008-10-12 7:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 23:59 Linux 2.6.27 Linus Torvalds
2008-10-11 21:03 ` Linux 2.6.27 will be a longtime supported kernel Adrian Bunk
2008-10-12 4:02 ` [stable] " Greg KH
2008-10-12 4:10 ` Adrian Bunk
2008-10-12 7:00 ` Willy Tarreau [this message]
2008-10-13 11:27 ` Américo Wang
2008-10-13 12:37 ` Adrian Bunk
2008-10-14 20:10 ` Lennart Sorensen
2008-10-14 21:04 ` [stable] " Greg KH
2008-10-14 22:43 ` Yinghai Lu
2008-10-14 22:48 ` Jiri Kosina
2008-10-14 23:23 ` Greg KH
2008-10-14 23:03 ` Chris Friesen
2008-10-15 2:27 ` Greg KH
2008-10-13 12:42 ` Alex Howells
2008-10-13 12:58 ` Nick Piggin
2008-10-14 17:12 ` Chris Friesen
2008-11-13 22:46 ` Linux 2.6.27 Bill Davidsen
2008-11-14 15:30 ` Stefan Richter
2008-11-14 17:56 ` Bill Davidsen
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=20081012070044.GM24654@1wt.eu \
--to=w@1wt.eu \
--cc=bunk@kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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
all inboxes | Powered by JetHome®