From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: Andres Salomon <dilinger@voxel.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-as1
Date: Thu, 13 Jan 2005 17:18:08 +0100 [thread overview]
Message-ID: <41E69F40.10607@bio.ifi.lmu.de> (raw)
In-Reply-To: <1105629960.9553.4.camel@localhost>
Andres Salomon wrote
> My plan is to include security fixes for a kernel or two behind what is
> the latest. Currently, I'm supporting (for Debian) 2.6.8 through
That would definitely help a lot. I always try to upgrade to a new major
release, but sometimes this is not easy. We have 60 hosts here and are,
for example, using Ati Radeons and nvidia Gforce cards. So when 2.6.10
came out, I couldn't just upgrade until patches came out that made
the fglrx and nv modules compile and work again.
So from time to time, there are reasons to stay with the former major
release for a while (and if it is only because one currently doesn't
have time for testing the new one) and I'm sure that I'm not the only
one with this problem. If at least one kernel behind the latest was
supplied with security fixes that would give people enough time to
test the new release without ruffle while still getting security
fixes for the former release.
> I do not plan to continue small bugfixes for older kernels too much
> longer after a new kernel is released; however, if people were to feed
> me patches for older kernels, I'd be more than happy to do releases.
I guess that for most people security fixes would already be enough,
or say, that's at least what you want in the first place...
I hope that many people make use of this tree and that is will be
included on the kernel.org page as official tree. It definitely is
a very useful tree!
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
next prev parent reply other threads:[~2005-01-13 16:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 8:37 2.6.10-as1 Andres Salomon
2005-01-13 10:09 ` 2.6.10-as1 Frank Steiner
2005-01-13 15:26 ` 2.6.10-as1 Andres Salomon
2005-01-13 16:18 ` Frank Steiner [this message]
2005-01-13 16:26 ` 2.6.10-as1 Phil Oester
2005-01-13 20:11 ` 2.6.10-as1 Daniel Drake
2005-01-13 18:48 ` 2.6.10-as1 Felipe Alfaro Solana
2005-01-14 3:15 ` 2.6.10-as1 Andres Salomon
2005-01-13 19:08 ` 2.6.10-as1 Andres Salomon
2005-01-14 8:05 ` 2.6.10-as1 Raphael Zimmerer
2005-01-14 14:20 ` 2.6.10-as1 Andres Salomon
2005-01-14 16:33 ` 2.6.10-as1 Frank Steiner
2005-01-14 23:31 ` 2.6.10-as1 Daniel Drake
2005-01-14 21:26 ` 2.6.10-as1 Andres Salomon
2005-01-15 2:41 ` 2.6.10-as1 Daniel Drake
2005-01-18 6:36 ` 2.6.10-as1 Frank Steiner
2005-01-24 17:10 ` 2.6.10-as1 / 2.4 security-only patchset? Pasi Kärkkäinen
2005-01-24 19:32 ` Marcelo Tosatti
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=41E69F40.10607@bio.ifi.lmu.de \
--to=fsteiner-mail@bio.ifi.lmu.de \
--cc=dilinger@voxel.net \
--cc=linux-kernel@vger.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