From: John Bradford <john@grabjohn.com>
To: scott@coyotegulch.com (Scott Robert Ladd)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.60 cheerleading...
Date: Wed, 12 Feb 2003 18:41:13 +0000 (GMT) [thread overview]
Message-ID: <200302121841.h1CIfDUe007962@darkstar.example.net> (raw)
In-Reply-To: <FKEAJLBKJCGBDJJIPJLJGELBELAA.scott@coyotegulch.com> from "Scott Robert Ladd" at Feb 12, 2003 01:17:27 PM
> > So, it's working great for me :)
>
> I always wonder what should be said by testers when beta software actually
> *works*. ;)
>
> I've been successfully running 2.5.60 on my Tycho system since a few minutes
> after Linus announced it. The major bugs I'd had in 2.5.59 were with Alsa,
> which seems to be running well in 2.5.60.
>
> I wonder if testers should post configs that worked, so developers can
> compare against configs that failed?
Feel free to open a 'bug report' on my bug database just to upload a
working .config - I.E. you can use it as a somewhat-organised, and
comment-onable .config storage repository, if that's any use.
http://grabjohn.com/kernelbugdatabase/
If there is sufficient interest, I can add some code to pick out the
common config options out of a set of config files, or whatever you
want. Just ask, and the feature will be, (eventually), added :-)
John.
next prev parent reply other threads:[~2003-02-12 18:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 15:52 2.5.60 cheerleading Jeff Garzik
2003-02-12 16:00 ` Paul Larson
2003-02-12 16:09 ` Jeff Garzik
2003-02-12 18:07 ` Dave Jones
2003-02-12 18:44 ` John Bradford
2003-02-12 18:17 ` Scott Robert Ladd
2003-02-12 18:41 ` John Bradford [this message]
2003-02-12 18:55 ` Dave Jones
2003-02-12 18:43 ` Paul Larson
2003-02-12 19:33 ` Edesio Costa e Silva
2003-02-13 15:29 ` Paul Larson
2003-02-13 15:54 ` Jörn Engel
2003-02-13 16:03 ` Dave Jones
2003-02-13 16:55 ` Paul Larson
2003-02-13 17:11 ` John Bradford
2003-02-13 18:04 ` Paul Larson
2003-02-13 18:23 ` John Bradford
2003-02-13 21:16 ` Paul Larson
2003-02-13 21:38 ` Jeff Garzik
2003-02-13 21:54 ` John Bradford
2003-02-13 21:57 ` Paul Larson
2003-02-13 22:11 ` John Bradford
2003-02-13 22:20 ` Valdis.Kletnieks
2003-02-13 22:39 ` Paul Larson
2003-02-13 22:43 ` Randy.Dunlap
2003-02-13 22:53 ` Paul Larson
2003-02-13 22:58 ` John Bradford
2003-02-14 6:36 ` Paul Larson
2003-02-20 22:29 ` Timothy D. Witham
2003-02-20 22:42 ` Jeff Garzik
2003-02-20 22:46 ` Timothy D. Witham
2003-02-14 1:21 ` Martin J. Bligh
2003-02-14 1:32 ` Linus Torvalds
2003-02-14 3:24 ` Mike Dresser
2003-02-14 9:08 ` John Bradford
2003-02-14 4:10 ` Werner Almesberger
2003-02-13 17:06 ` Jeff Garzik
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=200302121841.h1CIfDUe007962@darkstar.example.net \
--to=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@coyotegulch.com \
/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.