From: Thomas Voegtle <tv@lio96.de>
To: Greg KH <gregkh@suse.de>
Cc: "Éric Piel" <eric.piel@tremplin-utc.net>,
webmaster@kernel.org, LKML <linux-kernel@vger.kernel.org>,
stable@kernel.org
Subject: Re: Linux 2.6.27.28
Date: Sat, 25 Jul 2009 09:25:21 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.0907250906330.10172@er-systems.de> (raw)
In-Reply-To: <20090725033030.GA481@suse.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1341 bytes --]
Hi,
first of all: thank you for the stable kernels...
On Fri, 24 Jul 2009, Greg KH wrote:
> On Sat, Jul 25, 2009 at 01:49:53AM +0200, Éric Piel wrote:
>> Currently, there is no clue on www.kernel.org that 2.6.27 is a "long
>> term stable" kernel tree. Would it be possible to add a line to the page
>> pointing to the latest version of this type of tree? I'm sure some
>> people would love discovering that such thing exists :-)
>
> I'm curious as to why someone, if they were inclined to be using such a
> thing, wouldn't already know about this?
It even isn't called at linux-kernel-announce, except the latest stable
kernel.
So you have to read LKML, or follow the lwn.net news to track the
older stable kernel. Or always guessing: when there is a release of the
newer stable kernel (this is announced in linux-kernel-announce) then
there might be a release of the older one aswell...
> How many people really are relying on this .27 branch, becides the
> distros, these days? And if you are, why?
I'm one of that guys, having a server and one firewall and feeling
much better with a small optimized own-built kernel for that machines.
And both just work with this .27 branch, why should I change it to
2.6.30.y?
I don't need any of the new features and it won't be faster with 2.6.30 or
something else...
Thomas
next prev parent reply other threads:[~2009-07-25 7:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 22:27 Greg KH
2009-07-24 22:28 ` Greg KH
2009-07-24 23:49 ` Éric Piel
2009-07-25 1:50 ` J.H.
2009-07-25 3:30 ` Greg KH
2009-07-25 4:18 ` Bron Gondwana
[not found] ` <ck4l6511epc17ngfdu7qu8ln46b7op9lj9@4ax.com>
2009-07-25 5:26 ` Greg KH
2009-07-25 10:34 ` Grant Coady
2009-07-25 7:25 ` Thomas Voegtle [this message]
2009-07-25 10:00 ` Thomas Meyer
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=alpine.LNX.2.00.0907250906330.10172@er-systems.de \
--to=tv@lio96.de \
--cc=eric.piel@tremplin-utc.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=webmaster@kernel.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®