From: Adrian Bunk <bunk@kernel.org>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable@kernel.org
Subject: Re: Linux 2.6.27 will be a longtime supported kernel
Date: Mon, 13 Oct 2008 15:37:05 +0300 [thread overview]
Message-ID: <20081013123705.GF29938@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <20081013112701.GA12706@hack.voiplan.pt>
On Mon, Oct 13, 2008 at 12:27:01PM +0100, Américo Wang 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.
> >
> >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).
> >
> >It is intended to fill the niche for users who are not using
> >distribution kernels but want to use a regression-free kernel for a
> >longer time. It might be a small part of the userbase, but after the
> >experiences with 2.6.16 I can say that there are quite a few users
> >who appreciate such an offering.
> >
> >As people might have noted I wasn't able to do much kernel stuff
> >recently, and 2.6.16 also suffered from this. I'll bring 2.6.16 back
> >into shape and keep it maintained until at least mid-2009.
>
> Thanks for your work.
>
> I am just wondering why you only selected .16 and .27, not others?
> Are there some specical reasons why you did this?
If the question is why it isn't .26 or .28:
I'm checking whether my computer works fine with a kernel, and also
very slightly what distributions might use a kernel, but in the end
it's pretty random.
If the question is about the big gap between them:
I don't want to maintain 10 kernels at once, and also for getting fixes
from other kernel developers it's better when I don't do this for too
many kernels.
> Thank you.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-10-13 12:38 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
2008-10-13 11:27 ` Américo Wang
2008-10-13 12:37 ` Adrian Bunk [this message]
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=20081013123705.GF29938@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.com \
/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®