Re: too much untested code in new kernels

Patricia Cross (cross@gweep.lkg.dec.com)
Fri, 3 Jan 1997 09:10:38 -0500 (EST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Jim Nance: "Re: How to increat [sic.] max open files? (fwd)"
Previous message: Morgan Sarges: "Re: 2.1.20 -- oops in reboot"
In reply to: Bob Lorenzini: "2.1.20: pcmcia broke"
Next in thread: Philip Blundell: "Re: too much untested code in new kernels"
Reply: Philip Blundell: "Re: too much untested code in new kernels"

Roy P. Turner wrote:
> I may be wrong, but I thought the purpose of the dev kernels, is so that
> we, the willing, can test them and report bugs to the maintainers.

Yes, the development kernels are there so we can test them, but I really
don't think it's too much to ask that the person submitting a change at
least _compile_ it before turning it in. Why would anyone turn it a
change that they don't even know works on one single system?

-Trish

Next message: Jim Nance: "Re: How to increat [sic.] max open files? (fwd)"
Previous message: Morgan Sarges: "Re: 2.1.20 -- oops in reboot"
In reply to: Bob Lorenzini: "2.1.20: pcmcia broke"
Next in thread: Philip Blundell: "Re: too much untested code in new kernels"
Reply: Philip Blundell: "Re: too much untested code in new kernels"