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 for Android: free password hash cracker in your pocket

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

Message-Id: <200704300009.07257.rjw@sisk.pl>
Date:	Mon, 30 Apr 2007 00:09:06 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Alexey Dobriyan <adobriyan@...il.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Adrian Bunk <bunk@...sta.de>,
	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 Sunday, 29 April 2007 22:52, Alexey Dobriyan wrote:
> On Sun, Apr 29, 2007 at 10:18:10PM +0200, Rafael J. Wysocki wrote:
> > [For example, you can create a bugzilla entry with a link to the lkml.org copy
> > of the relevant message, so why to require the reporter to file the report with
> > the bugzilla himself?]
> 
> Last time I did this, bugzilla at osdl.org won't let me add original
> reporter to goddamn CC list. It would be el neat, because not everyone
> followed instructions and forwarding emails between reporter and
> bugzilla sucks.

That's related to what I said before.  The requirement that the addresses on
the CC list must be 'known' to bugzilla is deadly wrong in every case I can
imagine.
-
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/