> On 23 November 2014 at 21:27 Joe Perches <j...@perches.com> wrote: > > > On Sat, 2014-11-22 at 21:56 +0100, Fabian Frederick wrote: > > This script generates a graph based on errors/warnings/checks detected > > by checkpatch -f recursively on each files of a directory. > > Results are grouped by subfolders and pushed in gnuplot datasets. > > Why is this useful? > > Ingo's badly named script does something similar: > http://people.redhat.com/mingo/x86.git/code-quality > > just without the plots. > > btw: this line: > > $files = `find $statdir -name "*.c"`; > > should probably be > > $files = `git ls-files -- "$statdir/*.[ch]"`; >
This script was meant for reporting so it's just useful because of the graphs and the fact it can do all in one operation. Most of all, when someone does a talk and shows up some graph, it would be both easier and valid to tell it's using scripts/checkstat on kernel x.y rather than sparse operations someone won't easily reproduce. I don't think using directly git operations would be a good thing. This script could be used directly downloading tar.gz without it. (Of course Git could be bring nice options in future versions :)). Regards, Fabian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
