> I also. The bug database tries to convert the traditional many<->many > debugging process into a one<->one process. This surely results in a > lower cleanup rate. I think your suggestion of sending new bugs out to LKML has made a big dent in the one<->one problem already. Replacing all the default owner fields with mailing lists (either existing ones or new ones) instead of individuals would be another step in that direction, though there may be a few hurdles to deal with on the way to that. Yes, we probably also need an "email back in" interface as we've discussed before to take it up to many-many. > It is nice to have a record. But bugzilla is not a comfortable or > productive environment within which to drill down into and fix problems. OK ... But I'd rather try to fix it than to throw the baby out with the bath water. I don't believe it's "unfixable" - the concept of tracking bugs / problems and making sure they're closed out still seems sound to me. As an example, I've seen several examples already where I've pestered people about bugs that already had patches attatched to them that resulted in "oh, yeah, I forgot to actually submit that", and it's got fixes back into mainline. I find it somewhat hard to believe that just about every other big project (including open source ones) uses some form of bug tracking system, and yet Linux is somehow magically different ;-) M. - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
