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

On Friday 02 May 2008 13:30:23 Parag Warudkar wrote:
> On Fri, May 2, 2008 at 12:29 PM, Daniel Hazelton <dhazelton@...er.net>
> wrote: This is what Adrian was pointing
>
> > ... out and is exactly what shouldn't be happening.
>
> 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!

I have to admit that this is the truth. I've seen it myself. (Hell, I won't 
touch a bug-tracking system for that reason.)

> Also I feel that if maintainer refuse to fix something - that's a dead
> end as far as that particular bug is considered. We can try and track
> such bugs in different STATUS but there would have to be people
> interested in digging through such bugs and willing to fix it after
> the maintainer has given up. Which is possible but not likely.
>
> Parag

And I have to agree here. But there should be something that can be done 
to "coax" the maintainers that pull that kind of immature crap into acting 
mature and responsible.

DRH

-- 
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ