linux-kernel - Re: Linux 2.6.21

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 30 Apr 2007 01:18:57 +0200 (CEST)
From:	"Indan Zupancic" <indan@....nu>
To:	"Johannes Stezenbach" <js@...uxtv.org>
Cc:	"Adrian Bunk" <bunk@...sta.de>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Diego Calleja" <diegocg@...il.com>,
	"Andi Kleen" <andi@...stfloor.org>,
	"Chuck Ebbert" <cebbert@...hat.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.21

Hello,

On Mon, April 30, 2007 00:36, Johannes Stezenbach wrote:
> The lesson to learn is that there are some very valid
> reasons why bug reports get ignored (some not mentioned here),
> and there's nothing you can do about it. And it has nothing to
> do with the method or tool used for reporting or tracking.
>
> And I also think that ignoring bad bug reports _increases_
> the software quality, because you can use the saved time
> working on something productive. And it makes developers
> happier :-)
>
> [Just to avoid misunderstandings: By no means do I advocate
> ignoring *every* bug report. But ignoring the bad ones
> is just the sane thing to do.]

I don't know, but what about telling the hapless person who went
through the process of posting a bug what's wrong with the bug report?
Or is software quality the only thing you care about, and you don't
want to waste time on learning people to write better bug reports?

If you want to scare away bug reporters, just ignore their first (and
thus likely bad) bug report they write. There isn't much less motivating
than a deafening silence. Just compare it with writing a patch.

Though, in a sense, if the software quality is measured by the number of
bug reports, your tactic might "improve" it indeed.

That said, if someone is an obvious idiot, ignoring saves time. But I
think that's quite rare, and in general you should give the reporter
feedback, and then ignore the bug report. (Until it improves.)

Greetings,

Indan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/