From: Sean Bruno <sean.bruno@dsl-only.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Lee Revell <rlrevell@joe-job.com>,
webmaster@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Testing RC kernels [KORG]
Date: Tue, 02 Aug 2005 14:05:41 -0700 [thread overview]
Message-ID: <1123016741.24010.60.camel@jy.metro1.com> (raw)
In-Reply-To: <1123010465.1590.34.camel@localhost.localdomain>
On Tue, 2005-08-02 at 15:21 -0400, Steven Rostedt wrote:
> 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.
>
I would be more than willing to whip up an html how-to(and maintain it).
Is there any interest in this?
Sean
next prev parent reply other threads:[~2005-08-02 21:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2005-08-02 18:37 ` Testing RC kernels Michael Krufky
2005-08-03 10:52 ` Jiri Slaby
2005-08-03 0:00 Testing RC kernels [KORG] Shayne O'Connor
2005-08-03 0:41 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
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=1123016741.24010.60.camel@jy.metro1.com \
--to=sean.bruno@dsl-only.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=rostedt@goodmis.org \
--cc=webmaster@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
Powered by JetHome