From: John Bradford <john@grabjohn.com>
To: Valdis.Kletnieks@vt.edu
Cc: plars@linuxtestproject.org, linux-kernel@vger.kernel.org,
edesio@task.com.br, torvalds@transmeta.com
Subject: Re: 2.5.60 cheerleading...
Date: Thu, 13 Feb 2003 22:58:14 +0000 (GMT) [thread overview]
Message-ID: <200302132258.h1DMwFtH024363@darkstar.example.net> (raw)
In-Reply-To: <200302132220.h1DMKtFT011682@turing-police.cc.vt.edu> from "Valdis.Kletnieks@vt.edu" at Feb 13, 2003 05:20:55 PM
> > Since Linus hasn't chimed in yet, I'm guessing that's exactly what
> > happened. I'm not trying to improve his workflow, but rather the
> > workflow of anyone who might be interested in getting more involved in
> > 2.5 testing.
>
> What would help a lot of people (certainly me, at least), would be if
> somebody kept a well-publicized "already known errata" list along with
> (possibly unofficial) work-around patches. Something along the line of:
>
> compile fails in drivers/widget/fooby.c with error:
> undefined structure member 'blat' in line 1149.
> To fix: apply <this patch>
Well, you can do that with my bug database - just open a new bug
report for each compile failiure, upload a patch to the database, and
link the patch with the new bug. You can then collect together all
the relevant bug reports in to a confirmed bug for each kernel
version. You don't even have to duplicate bug reports if they occur in
multiple kernel versions.
John.
next prev parent reply other threads:[~2003-02-13 22:47 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
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 [this message]
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=200302132258.h1DMwFtH024363@darkstar.example.net \
--to=john@grabjohn.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=edesio@task.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@linuxtestproject.org \
--cc=torvalds@transmeta.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.