linux-kernel - Re: A proposal; making 2.6.20 a bugfix only version.

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]

Message-Id: <1163107915.3138.541.camel@laptopd505.fenrus.org>
Date:	Thu, 09 Nov 2006 22:31:55 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Andrew Morton <akpm@...l.org>, Jesper Juhl <jesper.juhl@...il.com>,
	Linus Torvalds <torvalds@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: A proposal; making 2.6.20 a bugfix only version.


> What if the quality of the bug report is good and the submitter is 
> responsive, and there's still zero reaction?
> 
> Let's make an example:

> 
> Since the first list I sent immediately after 2.6.19-rc1 was released, 
> kernel Bugzilla #7255 is part of my list of 2.6.19-rc regressions but 
> has gotten exactly zero developer responses.

where was the lkml mail for this?

> 
> What exactly were the mistakes of the submitter resulting in noone 
> caring about Bugzilla #7255?

he didn't post to lkml?


-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

-
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/