From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: David Newall <davidn@davidnewall.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
James Morris <jmorris@namei.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Willy Tarreau <w@1wt.eu>,
david@lang.hm, Stephen Clark <sclark46@earthlink.net>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
Tilman Schmidt <tilman@imap.cc>,
Valdis.Kletnieks@vt.edu, Mark Lord <lkml@rtr.ca>,
David Miller <davem@davemloft.net>,
jesper.juhl@gmail.com, yoshfuji@linux-ipv6.org, jeff@garzik.org,
linux-kernel <linux-kernel@vger.kernel.org>,
git@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Reporting bugs and bisection
Date: Tue, 15 Apr 2008 22:51:49 +0200 [thread overview]
Message-ID: <200804152251.51308.rjw@sisk.pl> (raw)
In-Reply-To: <4804B5D5.4090404@davidnewall.com>
On Tuesday, 15 of April 2008, David Newall wrote:
> Michael Kerrisk wrote:
> > On 4/15/08, David Newall <davidn@davidnewall.com> wrote:
> >
> >> James Morris wrote:
> >> > I don't know how to solve this, but suspect that encouraging the use of
> >> > reviewed-by and also including it in things like analysis of who is
> >> > contributing, selection for kernel summit invitations etc. would be a
> >> > start. At least, better than nothing.
> >>
> >> Would it be hard to keep count of the number of errors introduced by
> >> author and reviewer?
> >>
> >
> > I've found quite a few errors in kernel-userland APIs, but I'm not
> > sure that this sort of negative statistic would be helpful -- e.g.,
> > more productive developers probably also introduce more errors.
>
> We can already see which developers are more active. What we can't see
> is who is careless, which would be useful to know. It would also be
> useful to know who is careless in approving changes, because they share
> responsibility for those changes. It would be a good thing if this
> highlighted that some people are behind frequent buggy changes.
Well, even if someone introduces bugs relatively frequently, but then also
works with the reporters and fixes the bugs timely, it's about okay IMO.
The real problem is when patch submitters don't care for their changes any
more once the patches have been merged.
Thanks,
Rafael
next prev parent reply other threads:[~2008-04-15 20:52 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47FEADCB.7070104@rtr.ca>
[not found] ` <20080413121831.d89dd424.akpm@linux-foundation.org>
[not found] ` <20080413202118.GA29658@2ka.mipt.ru>
[not found] ` <200804132233.50491.rjw@sisk.pl>
[not found] ` <20080413205406.GA9190@2ka.mipt.ru>
[not found] ` <48028830.6020703@earthlink.net>
2008-04-13 23:51 ` Reporting bugs and bisection david
2008-04-14 0:36 ` Jakub Narebski
2008-04-14 4:39 ` Willy Tarreau
2008-04-14 5:39 ` Al Viro
2008-04-14 6:24 ` Andrew Morton
2008-04-14 6:39 ` David Miller
2008-04-14 6:43 ` David Miller
2008-04-14 7:23 ` Al Viro
2008-04-14 7:43 ` Al Viro
2008-04-14 8:04 ` Andrew Morton
2008-04-14 8:30 ` David Miller
2008-04-14 9:06 ` Christoph Hellwig
2008-04-14 9:46 ` Andi Kleen
2008-04-15 5:25 ` Bill Fink
2008-04-14 10:15 ` Andrew Morton
2008-04-14 10:41 ` David Miller
2008-04-14 17:35 ` Roman Shaposhnik
2008-04-14 12:08 ` Adrian Bunk
2008-04-14 14:43 ` Arjan van de Ven
2008-04-14 17:51 ` Andrew Morton
2008-04-14 18:24 ` Arjan van de Ven
2008-04-14 19:30 ` Ilpo Järvinen
2008-04-14 15:54 ` James Morris
2008-04-14 22:01 ` David Miller
2008-04-14 23:05 ` Andrew Morton
2008-04-15 4:55 ` Willy Tarreau
2008-04-15 13:18 ` Work WAS(Re: " jamal
2008-04-15 9:33 ` David Newall
2008-04-15 9:54 ` Michael Kerrisk
2008-04-15 14:04 ` David Newall
2008-04-15 20:51 ` Rafael J. Wysocki [this message]
2008-04-16 2:34 ` David Newall
2008-04-16 3:53 ` david
2008-04-16 9:06 ` David Newall
2008-04-16 11:02 ` Andi Kleen
2008-04-16 12:41 ` Stephen Clark
2008-04-16 4:29 ` Willy Tarreau
2008-04-16 12:13 ` Rafael J. Wysocki
2008-04-16 12:15 ` Sverre Rabbelier
2008-04-16 13:26 ` Adrian Bunk
2008-04-16 19:02 ` Andrew Morton
2008-04-16 19:43 ` Sverre Rabbelier
2008-04-16 19:55 ` Adrian Bunk
2008-04-17 13:50 ` J. Bruce Fields
2008-04-17 15:26 ` Adrian Bunk
2008-04-16 19:58 ` Alexey Dobriyan
2008-04-16 20:01 ` Arjan van de Ven
2008-04-16 19:39 ` Sverre Rabbelier
2008-04-16 20:16 ` Adrian Bunk
2008-04-16 20:53 ` Adrian Bunk
2008-04-16 21:05 ` Sverre Rabbelier
2008-04-16 21:25 ` Adrian Bunk
2008-04-16 20:04 ` Willy Tarreau
2008-04-16 20:55 ` Jakub Narebski
2008-04-16 21:17 ` Jesper Juhl
2008-04-17 17:04 ` David Newall
2008-04-17 19:09 ` Rafael J. Wysocki
2008-04-17 19:35 ` Ray Lee
2008-04-17 19:57 ` Sverre Rabbelier
2008-04-17 20:16 ` Al Viro
2008-04-17 20:38 ` Ray Lee
2008-04-17 20:53 ` Al Viro
2008-04-17 21:01 ` Ray Lee
2008-04-14 19:13 ` Rene Herman
2008-04-14 20:38 ` Andrew Morton
2008-04-14 22:18 ` Rene Herman
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=200804152251.51308.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=david@lang.hm \
--cc=davidn@davidnewall.com \
--cc=git@vger.kernel.org \
--cc=jeff@garzik.org \
--cc=jesper.juhl@gmail.com \
--cc=jmorris@namei.org \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sclark46@earthlink.net \
--cc=tilman@imap.cc \
--cc=viro@zeniv.linux.org.uk \
--cc=w@1wt.eu \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).