Messages in this thread | | | Date | Mon, 26 May 2008 11:36:09 +0200 | From | Ingo Molnar <> | Subject | Re: Top 10 bugs/warnings for the week of March 23rd, 2008 |
| |
* Arjan van de Ven <arjan@linux.intel.com> wrote:
>> At any rate, they have a bug in their proprietary module (news at >> 11). >> >> So, I don't think this should make the top ten. Do you have a way to >> sort tainted vs non-tainted, and only produce the top ten for >> untainted? > > yes absolutely; this is a question I'll have for the customers of the > data... do people want to see "only-tainted" in these top 10s? Right > now I mark them as such but leave them in. It's trivial for me to just > leave them out instead (the info is there, just a matter of not > counting)
i think they should be included, but perhaps abbreviated [into 1-2 lines] so that they do not hold us up.
We must not whitewash our bug statistics by intentionally excluding the harm that bin-only modules do to our users - but we can make them less visually intrusive, so that we can work on fixing the bugs we can fix.
Perhaps make sure it's top 10 of _our_ bugs, with the bin-only data mixed in as well (in a visually unintrusive way) to make the picture complete. I.e. list 20 bugs if 10 of them are bin-only modules.
Ingo
| |