linux-kernel - Re: How to reduce the number of open kernel bugs

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: <82e4877d0805021125y1e11deb4qaa57ac493cf41aba@mail.gmail.com>
Date:	Fri, 2 May 2008 14:25:47 -0400
From:	"Parag Warudkar" <parag.warudkar@...il.com>
To:	"Adrian Bunk" <bunk@...nel.org>
Cc:	"Daniel Hazelton" <dhazelton@...er.net>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: How to reduce the number of open kernel bugs

On Fri, May 2, 2008 at 2:01 PM, Adrian Bunk <bunk@...nel.org> wrote:
> On Fri, May 02, 2008 at 01:30:23PM -0400, Parag Warudkar wrote:
>  > I wasn't arguing that it is what should be happening - I was just
>  > pointing out that there are worse things than that routinely happen in
>  > distro bugzillas!
>
>  And the point is?
>

Point being that no one can force anyone to do anything in the setting
in which kernel developers work.
Distros have been doing this since ever and people have no choice but
to move on.
(Everybody works out of their own (or employer's) interest and
judgement - so telling some one to act otherwise will not be a whole
lot productive.)

>
>  You completely miss the point.

I am not - my point is that you can't do  much about it that will go
long way in resolving the issue.

>  And in any case, being more friendly to a bug submitter.

Well again -  you can't force people to do something like that. In
your example it would amount to the maintainer going against his/her
own judgement - however wrong it is to you and me, to the person who
can actually fix it - it's not a possibility. So you have to just
accept it and reassign it to some one else who is interested/capable -
for that I suggested tracking such bugs under a new STATUS.

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