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]
Date:	Tue, 13 May 2008 17:10:51 +0200
From:	Rene Herman <rene.herman@...access.nl>
To:	Jonathan Corbet <corbet@....net>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Tracking and crediting bug reporters

On 12-05-08 19:27, Jonathan Corbet wrote:

> So here's what we would like to try instead.  Whenever somebody sends up a
> patch fixing a reported bug, the name of the person who reported the bug
> would be immortalized with this tag:
> 
> 	Reported-by: A. Bug Reporter <email@...s.here>
> 
> In particular, reporters who work with the developers toward the resolution
> of the bug should be thanked in this way.  If we wanted to take things
> further, perhaps we could add a Bisected-by: tag for really hard-core
> helpers.

Ingo Molnar recently already used the latter:

http://marc.info/?l=linux-kernel&m=121032355203154&w=4

and a reply of mine consisted of now also needing a Reported-By:

http://marc.info/?l=linux-kernel&m=121037403515110&w=4

I must say the Bisected-by thing did feel a bit childish ("ah, I'm not 
in it to get the bug fixed but to get my name mentioned!") but hey, I 
find things to be offended over easily. From the example it does seem 
you probably want both if you have one; if reporter, nailer-downer and 
fixer are three seperate people.

Rene.
--
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