From: "Shayne O'Connor" <forums@machinehasnoagenda.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Testing RC kernels [KORG]
Date: Wed, 03 Aug 2005 10:00:45 +1000 [thread overview]
Message-ID: <42F0092D.7040601@machinehasnoagenda.com> (raw)
>> Thanks for testing the RCs, we need more users to do that.
>>
>> If any of your hardware stops working, make sure to report it, don't
>> assume that it will fix itself! Assume you're the first to notice the
>> bug.
>
> I've been complaining about this for some time. Kernel.org really needs
> to show more information about the rc kernels and how to create them.
> We want more testers, but I wonder how many people go through the above
> steps and just give up when things don't work. Luckly Sean was nice
> enough to email the LKML and ask.
>
> My main gripe is that there's no link to 2.6.12 which is what most of
> the other patches go against.
>
> -- Steve
yeah, it took me a while to figure out how to patch the kernel with the
latest RC ... i'm finally there, though, and am addicted now to testing
each bleeding edge kernel :(
shayne
next reply other threads:[~2005-08-03 0:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 0:00 Shayne O'Connor [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-03 0:41 Testing RC kernels [KORG] Bodo Eggert
2005-08-03 4:21 ` H. Peter Anvin
2005-08-03 4:31 ` Michael Krufky
2005-08-03 4:57 ` H. Peter Anvin
2005-08-03 19:48 ` Bodo Eggert
2005-08-02 18:33 Testing RC kernels Sean Bruno
2005-08-02 18:36 ` Lee Revell
2005-08-02 18:36 ` Sean Bruno
2005-08-02 18:54 ` Lee Revell
2005-08-02 19:21 ` Testing RC kernels [KORG] Steven Rostedt
2005-08-02 21:05 ` Sean Bruno
2005-08-02 21:27 ` Michael Krufky
2005-08-03 2:04 ` Gene Heskett
2005-08-03 2:13 ` Randy.Dunlap
2005-08-03 2:35 ` Steven Rostedt
2005-08-03 3:30 ` Gene Heskett
2005-08-03 21:52 ` Andrew James Wade
2005-08-04 0:02 ` John Stoffel
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=42F0092D.7040601@machinehasnoagenda.com \
--to=forums@machinehasnoagenda.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.