public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Diego Calleja <diegocg@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	davem@davemloft.net
Subject: Re: Who reverted 2.6.25 - stats
Date: Fri, 2 May 2008 17:08:08 +0200	[thread overview]
Message-ID: <20080502170808.25283f01.diegocg@gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0805021332510.6463@fbirervta.pbzchgretzou.qr>

El Fri, 2 May 2008 14:16:19 +0200 (CEST), Jan Engelhardt <jengelh@medozas.de> escribió:

> following the implied "suggestion" of David Miller to track reverts in 
> http://marc.info/?l=linux-kernel&m=120959059828048&w=2 , I stitched 
> together a short script that evaluates the commit log summary and prints 
> a overview who has the most reverts and who got reverted most. There are 
> surprisingly few revert commits -- currently, perhaps because, as he 
> says, a "reluctance to even suggest reverts".

But what exactly those numbers mean?

A big number of reverts can mean that a developer usually submits unstable
stuff. But it can also mean that a developer cares so much about stability
that he'd rather revert, fix it and try to merge it in the next development
cycle. The "bad" maintainer that submits unstable stuff may try to fix
the reported bug instead of reverting it (but he won't fix the other 
undiscovered bugs that are still there because the code was not tested
well enought)

I don't think those numbers are very useful. Even the "number of bug reports
filed against the code of a given developer" is not considered meaningful as
measurement of good programming.

      parent reply	other threads:[~2008-05-02 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 12:16 Who reverted 2.6.25 - stats Jan Engelhardt
2008-05-02 12:39 ` Stefan Richter
2008-05-02 15:08 ` Diego Calleja [this message]

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=20080502170808.25283f01.diegocg@gmail.com \
    --to=diegocg@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jengelh@medozas.de \
    --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