Messages in this thread | | | Date | Wed, 16 Apr 2008 13:01:08 -0700 | From | Arjan van de Ven <> | Subject | Re: Reporting bugs and bisection |
| |
On Wed, 16 Apr 2008 12:02:47 -0700 Andrew Morton <akpm@linux-foundation.org> 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
| |