In article <20021203121521.GB30431@suse.de>,
Dave Jones <davej@codemonkey.org.uk> wrote:
| "xxx doesn't work in 2.5.47", then Rusty's module rewrite happened,
| and the tester didn't (or couldn't) see if it got fixed in subsequent
| kernels. I'll send out pings to such reports when they get to something
| like 5 kernels old. If the problem then doesn't get re-ACKed, I'll
| close it. Any objections?
Since you are doing the work, you should set your own policy. I might
suggest that if we revert the module stuff to something working in
fewer than five versions you might ping then, and you might wait to
drop stuff of the "xxx fails in 2.5.47 as a module" until modules work
again or we officially go to a monolythic kernel.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. - 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/
This archive was generated by hypermail 2b29 : Sat Dec 07 2002 - 22:00:16 EST