From: klink@clouddancer.com (Colonel)
To: linux-kernel@vger.kernel.org
Subject: Re: Re: Please tag tested releases of the 2.4.x kernel
Date: Sat, 1 Dec 2001 11:51:30 -0800 (PST) [thread overview]
Message-ID: <20011201195130.159787843A@phoenix.clouddancer.com> (raw)
In-Reply-To: <9uagu8$3a7$1@phoenix.clouddancer.com>
In-Reply-To: <200112011200.fB1C0m711338@ns.caldera.de> <20011201113734.5187E38329@fever.semiotek.com> <9uagu8$3a7$1@phoenix.clouddancer.com>
In clouddancer.list.kernel, you wrote:
>
>In article <20011201113734.5187E38329@fever.semiotek.com> you wrote:
>> And the kernels on kernel.org *are* tested, by lots of people, by kernel
>> developers, by lots of ordinary folks even. I bet right after theren's
>> an announce on slashdot you see lots of traffic on the ftp/http sites.
>
>The problem is that there is absoloutly no defined QA-cycle for these
>kernels. Please take a look at what distributors (at least most, I know
>at least one counter-example):
Actually, I find it pretty easy to sort out which to run. Just look
at the email subjects of lkml for a few days after release. Bad stuff
is rather rapidly detected, so "no news is good news". As for
protecting the info on your hard disk, you do make backups of course?
--
Windows 2001: "I'm sorry Dave ... I'm afraid I can't do that."
prev parent reply other threads:[~2001-12-01 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 11:37 Justin Wells
2001-12-01 12:00 ` Christoph Hellwig
2001-12-01 19:51 ` Colonel [this message]
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=20011201195130.159787843A@phoenix.clouddancer.com \
--to=klink@clouddancer.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
all inboxes | Powered by JetHome®