From: "David L. Parsley" <parsley@linuxjedi.org>
To: laughing@shared-source.org
Cc: linux-kernel@vger.kernel.org
Subject: Clear indication of stable -ac kernels?
Date: Wed, 03 Oct 2001 22:22:21 -0400 [thread overview]
Message-ID: <3BBBC7DD.E4FB1255@linuxjedi.org> (raw)
Hi Alan,
I was just wondering if you might stamp your kernel releases clearly
with some indication of stable/probably stable/don't bet the farm - or
some such. I've got a big-ish (2 X 1Ghz, 1.5G) multi-user terminal
server that's having bits of flakiness (which I suspect are recently
fixed), and could probably stand a kernel upgrade. I'm guessing that
2.4.10-ac4 is probably a good bet, but I'd sure be happy if you'd make
clear statements to that effect. ;-) (i.e., when Linus releases
something non-pre, I assume he means 'I think this is stable' - even
though he's not always right, I still feel better trying those in
production than any of his -pre's)
regards,
David
--
David L. Parsley
Network Administrator, Roanoke College
"First they ignore you, then they laugh at you, then
they fight you, then you win." - Gandhi
reply other threads:[~2001-10-04 2:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3BBBC7DD.E4FB1255@linuxjedi.org \
--to=parsley@linuxjedi.org \
--cc=laughing@shared-source.org \
--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