Re: Reporting bugs and bisection
- From
- Jesper Juhl <jesper.juhl@gmail.com>
- Date
- Apr 16, 2008, 21:17 UTC
- Message-ID
- <9a8748490804161417n4ad6c1den54ccd302831a66c6@mail.gmail.com>
- In-Reply-To
- <bd6139dc0804160515s64a36748v49556c56d475dda4@mail.gmail.com>
On 16/04/2008, Sverre Rabbelier <alturin@gmail.com> wrote: ...
Show 6 quoted lines
> Git is participating in Google Summer of Code this year and I've > proposed to write a 'git statistics' command. This command would allow > the user to gather data about a repository, ranging from "how active > is dev x" to "what did x work on in the last 3 weeks". It's main > feature however, would be an algorithm that ranks commits as being > either 'buggy', 'bugfix' or 'enhancement'.
Interresting. Just be careful results are produced for the big picture and not used to point fingers at individuals.
>(There are several clues > that can aid in determining this, a commit msg along the lines of > "fixes ..." being the most obvious.)
One thing I thought of is that the more "Acked-by", "Reviewed-by" and "Signed-off-by" lines a patch has, the better reviewed we can probably assume it to be and thus the probability of it having introduced a bug probably drops slightly compared to other less-reviewed patches... or maybe not, but at least it's something to think about :-)
-- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html