From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Adrian Bunk <bunk@kernel.org>
Cc: Am??rico Wang <xiyou.wangcong@gmail.com>,
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: Tue, 14 Oct 2008 16:10:54 -0400 [thread overview]
Message-ID: <20081014201054.GD22851@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20081013123705.GF29938@cs181140183.pp.htv.fi>
On Mon, Oct 13, 2008 at 03:37:05PM +0300, Adrian Bunk wrote:
> 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.
So any distributions using .27 by the looks of it? It looks like Debian
is going with .26 for the 5.0 release, so if nothing else they will have
to be maintaining that one for quite a while. I suppose having someone
maintain .27 makes sense in that case.
--
Len Sorensen
next prev parent reply other threads:[~2008-10-14 20:11 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
2008-10-14 20:10 ` Lennart Sorensen [this message]
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=20081014201054.GD22851@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=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
Powered by JetHome