From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764277AbYDPUQx (ORCPT ); Wed, 16 Apr 2008 16:16:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757673AbYDPUQR (ORCPT ); Wed, 16 Apr 2008 16:16:17 -0400 Received: from smtp5.pp.htv.fi ([213.243.153.39]:38303 "EHLO smtp5.pp.htv.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756779AbYDPUQM (ORCPT ); Wed, 16 Apr 2008 16:16:12 -0400 Date: Wed, 16 Apr 2008 23:16:06 +0300 From: Adrian Bunk To: sverre@rabbelier.nl Cc: git@vger.kernel.org, linux-kernel , James Morris , Al Viro , Andrew Morton , Willy Tarreau , david@lang.hm, Stephen Clark , Evgeniy Polyakov , "Rafael J. Wysocki" , Tilman Schmidt , Valdis.Kletnieks@vt.edu, Mark Lord , David Miller , jesper.juhl@gmail.com, yoshfuji@linux-ipv6.org, jeff@garzik.org, netdev@vger.kernel.org, David Newall Subject: Re: Reporting bugs and bisection Message-ID: <20080416201606.GS1677@cs181133002.pp.htv.fi> References: <20080414043939.GA6862@1wt.eu> <20080414053943.GU9785@ZenIV.linux.org.uk> <20080413232441.e216a02c.akpm@linux-foundation.org> <20080414072328.GW9785@ZenIV.linux.org.uk> <4804765B.2070300@davidnewall.com> <20080416132634.GA545@cs181133002.pp.htv.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 16, 2008 at 09:39:41PM +0200, Sverre Rabbelier wrote: > On Wed, Apr 16, 2008 at 3:26 PM, Adrian Bunk wrote: >... > > E.g. if you look at commit f743d04dcfbeda7439b78802d35305781999aa11 > > (ide/legacy/q40ide.c: add MODULE_LICENSE), how could you determine > > automatically that it is a bugfix, and the commit that introduced > > the bug? > > Well, a dead giveaway would be: > "http://bugzilla.kernel.org/show_bug.cgi?id=10124" Which could be "There is no driver for my TV card in the kernel." > > You can always get some data, but if you want to get usable statistics > > you need explicit tags in the commits, not some algorithm that tries > > to guess. > > As said above, I don't agree, you can 'guess' very reliably on a large > dataset. Also, most commits are already 'tagged' in some way or > another. The trick is to find the pattern in this tagging and use it. > > I hope this clears things up a bit, I hope you are aware of the non-technical implications if the results don't match reality? E.g. I am proud that my commits do virtually never introduce bugs, so any results someone publishes about what I do should better be right or my first thoughts are somewhere between "fist" and "lawyer". [1] > Cheers, > > Sverre Rabbelier cu Adrian [1] my actual reaction might only be an angry email, but I hope you get the point that wrong results can really piss off people -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed