> > is too noisy and many key people dont read it.
>
> ...but if you are working with the code and you see something change
> the mailing list is the place to ask, correct?
Or its submitter - thyats why names in changelogs are so important
> > Many kernel bug reports end up invisible to some of the developers.
>
> Many kernel developers don't read LKML.
> Isn't that their flaw?
Not really. If they read lk they would have no time to fix bugs.
> I sincerely challenge you to propose a method for centralizing
> bug tracking in the Linux kernel that _can_ be used by the
> community as a whole. That means something that Linus would use
> _and_ somebody who doesn't subscribe to LKML can use to find out
> why he can't compile loop.o on his redhat 7.0 system with the
> kernel he got from kernel.org a few weeks ago.
You don't centralise it. You ensure the data is in common(ish) formats
and let the search tools improve. Would you build google by making all
the web run at one site ?
-
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 : Sun Dec 23 2001 - 21:00:17 EST