From: "Mark Haney" <mhaney@ercbroadband.org>
To: <gentoo-amd64@lists.gentoo.org>
Subject: [gentoo-amd64] 2.6.18 kernel
Date: Wed, 01 Nov 2006 12:23:28 -0500 [thread overview]
Message-ID: <4548D810.3010103@ercbroadband.org> (raw)
Is it just me or is the .18 kernel slow in getting unmasked? I don't
recall any other releases taking as long to be marked stable, but then I
haven't been quite as anxious to test a new kernel as I have been for
.18. I'm sure people are running it, so I ask, how is it? Has it been
stable or is it not quite ready for us 'less than hardcore' testers?
--
Ceterum censeo, Carthago delenda est.
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
--
gentoo-amd64@gentoo.org mailing list
next reply other threads:[~2006-11-01 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 17:23 Mark Haney [this message]
2006-11-01 17:52 ` [gentoo-amd64] 2.6.18 kernel Andrei Slavoiu
2006-11-01 17:53 ` Hemmann, Volker Armin
2006-11-03 9:20 ` Peter Humphrey
2006-11-02 0:42 ` [gentoo-amd64] " Duncan
2006-11-02 17:30 ` Christoph Mende
2006-11-02 16:51 ` Barry.SCHWARTZ
2006-11-03 4:33 ` Vladimir G. Ivanovic
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=4548D810.3010103@ercbroadband.org \
--to=mhaney@ercbroadband.org \
--cc=gentoo-amd64@lists.gentoo.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