From: Christoph Hellwig <hch@ns.caldera.de>
To: jread@semiotek.com (Justin Wells)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Please tag tested releases of the 2.4.x kernel
Date: Sat, 1 Dec 2001 10:41:28 +0100 [thread overview]
Message-ID: <200112010941.fB19fSb24081@ns.caldera.de> (raw)
In-Reply-To: <20011130220451.9D5AD38326@fever.semiotek.com>
In article <20011130220451.9D5AD38326@fever.semiotek.com> you wrote:
>
> It would be great if on kernel.org there were a note indicating which
> releases of the linux kernel had been favourably received.
>
> If you could organize a bit you could even mark a release as "TESTED",
> or even "APPROVED". All it would mean is that after it had been out for
> a week or two nobody found any really serious problems.
Approved kernel are usually come in files ending in i386.rpm,
ia64.rpm or .deb.
Come on, no one expects stock kernel to be tested. Distributors
on the other hand spend a lot of effort on testing their releases,
so go for a distribution kernel if you need something tested. Really.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-12-01 9:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-30 22:04 Please tag tested releases of the 2.4.x kernel Justin Wells
2001-11-30 23:15 ` Mike Fedyk
2001-12-01 0:28 ` Mike Fedyk
2001-12-01 9:41 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-01 1:05 willy tarreau
2001-12-01 1:10 ` Mike Fedyk
2001-12-01 2:42 ` Ian Stirling
2001-12-01 2:53 ` Mike Fedyk
2001-12-01 11:31 ` Miquel van Smoorenburg
2001-12-02 23:38 Justin Wells
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=200112010941.fB19fSb24081@ns.caldera.de \
--to=hch@ns.caldera.de \
--cc=jread@semiotek.com \
--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