public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Sean Bruno <sean.bruno@dsl-only.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Testing RC kernels
Date: Tue, 02 Aug 2005 14:54:41 -0400	[thread overview]
Message-ID: <1123008881.12562.16.camel@mindpipe> (raw)
In-Reply-To: <1123007814.24010.45.camel@jy.metro1.com>

On Tue, 2005-08-02 at 11:36 -0700, Sean Bruno wrote:
> On Tue, 2005-08-02 at 14:36 -0400, Lee Revell wrote:
> > On Tue, 2005-08-02 at 11:33 -0700, Sean Bruno wrote:
> > > <noob question>
> > > 
> > > I have been trying to test the 2.6.13 and can't quite get the patches
> > > applied cleanly.
> > > 
> > > What kernel version (full kernel source tar ball) should I be using to
> > > apply the patches(rc5) with?  Is it 2.6.12.3?
> > 
> > No, 2.6.12.
> > 
> > Lee
> > 
> 
> Ah!  Thanks.

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.

Lee



  reply	other threads:[~2005-08-02 18:54 UTC|newest]

Thread overview: 15+ 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 [this message]
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
2005-08-02 18:37 ` Testing RC kernels Michael Krufky
2005-08-03 10:52   ` Jiri Slaby

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=1123008881.12562.16.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sean.bruno@dsl-only.net \
    /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