public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Adrian Bunk <bunk@kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Tracking and crediting bug reporters
Date: Sun, 18 May 2008 01:18:25 +0200	[thread overview]
Message-ID: <482F67C1.2010809@keyaccess.nl> (raw)
In-Reply-To: <20080517225325.GD8140@cs181133002.pp.htv.fi>

On 18-05-08 00:53, Adrian Bunk wrote:

> On Fri, May 16, 2008 at 10:35:43AM -0600, Jonathan Corbet wrote:
>> [Operating in delayed response mode, sorry...]
>>
>> Adrian Bunk <bunk@kernel.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?

Literal Bisected-by might not make for a very good tag. Bisection is a 
way to pin down a bug; just one of them. So say person A reports and 
person B says "Hey, I know what that is. Try reverting foo." B then 
doesn't fit the tag while the only difference is that B was clever 
enough to not need a bisection. So if this is about giving credit; 
Tracked-down-by maybe? Something else?

Rene.

  reply	other threads:[~2008-05-17 23:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12 17:27 Tracking and crediting bug reporters Jonathan Corbet
2008-05-12 17:48 ` Cyrill Gorcunov
2008-05-12 18:20 ` Alan Cox
2008-05-12 20:52   ` David Miller
2008-05-12 21:08     ` Alan Cox
2008-05-13 10:51       ` Andi Kleen
2008-05-13 10:50         ` Alan Cox
2008-05-13 16:36           ` Jeff Garzik
2008-05-12 20:54   ` Jiri Slaby
2008-05-12 21:11     ` Alan Cox
2008-05-12 21:59       ` Rafael J. Wysocki
2008-05-12 18:27 ` Rik van Riel
2008-05-12 19:11 ` Rafael J. Wysocki
2008-05-13 10:28 ` Adrian Bunk
2008-05-16 16:35   ` Jonathan Corbet
2008-05-17 22:53     ` Adrian Bunk
2008-05-17 23:18       ` Rene Herman [this message]
2008-05-18 19:51       ` Jonathan Corbet
2008-05-13 15:10 ` Rene Herman
2008-05-14 17:30   ` Stefan Richter
2008-05-21 10:41 ` Pavel Machek
2008-05-21 13:34   ` Johannes Weiner
2008-05-21 13:46     ` Pekka Enberg
  -- strict thread matches above, loose matches on Subject: below --
2008-05-15  8:02 Roland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=482F67C1.2010809@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=bunk@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox