linux-kernel - Re: Who reverted 2.6.25

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] [day] [month] [year] [list]

Date:	Fri, 2 May 2008 17:08:08 +0200
From:	Diego Calleja <diegocg@...il.com>
To:	Jan Engelhardt <jengelh@...ozas.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	davem@...emloft.net
Subject: Re: Who reverted 2.6.25 - stats

El Fri, 2 May 2008 14:16:19 +0200 (CEST), Jan Engelhardt <jengelh@...ozas.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.
--
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/