public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@saeurebad.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Jonathan Corbet <corbet@lwn.net>, linux-kernel@vger.kernel.org
Subject: Re: Tracking and crediting bug reporters
Date: Wed, 21 May 2008 15:34:35 +0200	[thread overview]
Message-ID: <87r6bv4w7o.fsf@saeurebad.de> (raw)
In-Reply-To: <20080521104145.GB4948@ucw.cz> (Pavel Machek's message of "Wed, 21 May 2008 12:41:45 +0200")

Hi,

Pavel Machek <pavel@ucw.cz> writes:

> Hi!
>
>> 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@goes.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
>
> I believe we have enough tags already. Plus, if the reporter really
> works with the developer till the end, there's already accepter
> Tested-by: flag, right?

I would more argue to remove Tested-by completely because it does not
tell much.  Code is not bugfree just because someone compiled and ran
it.  And if it breaks on some other systems later on, what does it help
if you know someone tested it?  It still breaks.  And you can not even
blame the tester because of his luck of a working configuration.

While a Reported-by in this case credits a person reporting a bug.  Just
that.  And perhaps that the report was good enough to make a fix.

	Hannes

  reply	other threads:[~2008-05-21 13:35 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
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 [this message]
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=87r6bv4w7o.fsf@saeurebad.de \
    --to=hannes@saeurebad.de \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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