linux-kernel - Re: Tracking and crediting bug reporters

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: <20080517225325.GD8140@cs181133002.pp.htv.fi>
Date:	Sun, 18 May 2008 01:53:25 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Jonathan Corbet <corbet@....net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Tracking and crediting bug reporters

On Fri, May 16, 2008 at 10:35:43AM -0600, Jonathan Corbet wrote:
> [Operating in delayed response mode, sorry...]
> 
> Adrian Bunk <bunk@...nel.org> wrote:
> 
> > In which format do you want data for commits already in 2.6.26?
> 
> I hadn't thought about trying to backfill data for existing commits;
> that sounds like a fair amount of work for coverage which could still be
> somewhat spotty.  If you have the data at hand, though, then a simple
> file of the form
> 
> 	commit-id  full-name <email>

How to indicate whether it's a Reported-by or a Bisected-by?

> could be dealt with. But is it really worth the effort?

Not sure whether you don't consider it important that the data you 
publish is correct, but I will contribute the data I know about.

> Thanks,
> 
> jon

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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