From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752793AbYDPUBx (ORCPT ); Wed, 16 Apr 2008 16:01:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756456AbYDPUBj (ORCPT ); Wed, 16 Apr 2008 16:01:39 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:34965 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762254AbYDPUBi (ORCPT ); Wed, 16 Apr 2008 16:01:38 -0400 Date: Wed, 16 Apr 2008 13:01:08 -0700 From: Arjan van de Ven To: Andrew Morton Cc: Adrian Bunk , sverre@rabbelier.nl, git@vger.kernel.org, linux-kernel@vger.kernel.org, jmorris@namei.org, viro@zeniv.linux.org.uk, w@1wt.eu, david@lang.hm, sclark46@earthlink.net, johnpol@2ka.mipt.ru, rjw@sisk.pl, tilman@imap.cc, Valdis.Kletnieks@vt.edu, lkml@rtr.ca, davem@davemloft.net, jesper.juhl@gmail.com, yoshfuji@linux-ipv6.org, jeff@garzik.org, netdev@vger.kernel.org, davidn@davidnewall.com Subject: Re: Reporting bugs and bisection Message-ID: <20080416130108.4eda6c2c@laptopd505.fenrus.org> In-Reply-To: <20080416120247.c665859c.akpm@linux-foundation.org> References: <20080413205406.GA9190@2ka.mipt.ru> <48028830.6020703@earthlink.net> <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> <20080416120247.c665859c.akpm@linux-foundation.org> Organization: Intel X-Mailer: Claws Mail 3.2.0 (GTK+ 2.12.5; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 16 Apr 2008 12:02:47 -0700 Andrew Morton wrote: > > > At least with the data we have currently in git it's impossible to > > figure that out automatically. > > > > 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? > > > > 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. > > Well yes. One outcome of the project would be to tell us what > changes we'd need to make to our processes to make such data > gathering more effective. also.. "what is a bugfix" is an interesting thing... for some things it's very easy. For others.. it's really hard to draw a solid line where bugs stop and features start. (for example, is a missing cpu id in oprofile a bugfix ("oprofile doesn't work") or a feature ("new cpu support"). This one is one of the more simple ones even...) -- If you want to reach me at my work email, use arjan@linux.intel.com For development, discussion and tips for power savings, visit http://www.lesswatts.org