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]

Message-ID: <20070429212756.GA14857@redhat.com>
Date:	Sun, 29 Apr 2007 17:27:56 -0400
From:	Dave Jones <davej@...hat.com>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Markus Rechberger <mrechberger@...il.com>,
	Diego Calleja <diegocg@...il.com>,
	Chuck Ebbert <cebbert@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.21

On Sun, Apr 29, 2007 at 02:05:42AM +0200, Adrian Bunk wrote:
 > On Sat, Apr 28, 2007 at 04:40:31PM -0700, Linus Torvalds wrote:
 > >...
 > > What's the difference between bugzilla and lkml.org? Both have search 
 > > buttons. Both archive the old stuff. Both can be pointed to.
 > 
 > Mailing lists don't track bugs.

There's no reason they can't.  Store them in folders 'fixed' 'pending'
'notabug' etc. Move mails between them when states change.
reply-to them when necessary. Bounce them. Add people to Ccs. etc. etc.

The only remaining piece of the puzzle is "how does everyone see the
states of the various pools", which could be solved in a number of
ways, daily uploads to a place on kernel org for eg.

Hell, you could store them in a git tree if it came to it.
That would also solve the problem for those with an aversion
to web browsers to see bugs :-)

	Dave

-- 
http://www.codemonkey.org.uk
-
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/