| On Thu, 13 Feb 2003 15:57:56 CST, Paul Larson said:
|
| > 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>
Yes, I agree, that would be helpful.
I try to keep current lkml/etc patches for fixes/cleanups to the
latest kernel, and I've thought about a way to post them, but it's
too time-consuming a task, especially when it's not one's job
to do that.
| On Thu, 13 Feb 2003 22:11:17 +0000 (GMT), John Bradford said:
|
| > You can always use 2.5.X-BK1 to get the fixes that we would probably
| > have been in 2.5.X if Linus had done more extensive testing on it
| > before releasing it.
|
| Almost but not quite what I meant - unless -BK1 is reserved for after-release
| whoops and doesn't contain "new stuff for release N+1". If -BK1 is only
| bugfixes, that would be good.
-- ~Randy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/