From: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Vendor kernels unpakced
Date: Fri, 10 Aug 2001 22:46:55 +0200 [thread overview]
Message-ID: <01081022465500.02522@idun> (raw)
In-Reply-To: <2167D6D1AACDD31196BE0008C7CF24DDAE0A18@issexc01.solthree.com>
In-Reply-To: <2167D6D1AACDD31196BE0008C7CF24DDAE0A18@issexc01.solthree.com>
Am Freitag, 10. August 2001 21:29 schrieb Phil Kos:
> > Just as it makes no sense to run a not-up-to-date release
> > kernel, it makes
> > no sense to keep anything but the very last on line. Just MVHO.
>
> I beg to differ, Herr Doktor von Brand. It makes more sense to run a
> not-up-to-date release kernel than it does to slavishly update to every new
> release without any pressing need for new features or functionality. Don't
> fall into the commercial software trap of "it's newer, so it *must* be
> better!"--here be tygers...
The problem is not what people should be running. The kernels people are
actually running are relevant. Any kernel on a CD sold in the last ~3 years
is run and bug reports will arrive.
If you choose to ignore anything but the latest standard kernels you loose a
large number of testers and bugs will go unnoticed longer.
Regards
Oliver
next prev parent reply other threads:[~2001-08-10 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-10 19:29 [ANNOUNCE] Vendor kernels unpakced Phil Kos
2001-08-10 20:46 ` Oliver Neukum [this message]
2001-08-10 21:34 ` Rik van Riel
2001-08-10 22:09 ` Kent Borg
-- strict thread matches above, loose matches on Subject: below --
2001-08-10 12:51 Christoph Hellwig
2001-08-10 13:09 ` Marco Colombo
2001-08-10 13:12 ` Christoph Hellwig
2001-08-10 13:47 ` Dave Jones
2001-08-10 13:47 ` Marco Colombo
2001-08-10 13:55 ` Horst von Brand
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=01081022465500.02522@idun \
--to=oliver.neukum@lrz.uni-muenchen.de \
--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