Some 4.12 development statistics

Posted Jul 30, 2017 15:31 UTC (Sun) by andy_shev (subscriber, #75870)
Parent article: Some 4.12 development statistics

I didn't check myself so the following question. Imagine that a maintainer does

% sed -i -e 's/old_api_call/new_api_call/g' <list of affected files>

If number of list of affected files greate than let's say 100 she or he immediatelly poped up in the statistics, right? But it's not what we would like to see there for my point of view.

Metrics

Posted Jul 30, 2017 19:09 UTC (Sun) by corbet (editor, #1) [Link] (3 responses)

Nothing I've done here counts the number of affected files, so not necessarily. But I'll freely admit that the metrics used here — changesets and changed lines — are awful. I'd sure like to find something better if anybody has any good ideas.

Metrics

Posted Jul 31, 2017 2:55 UTC (Mon) by pabs (subscriber, #43278) [Link] (1 responses)

Maybe something based on tokens using cregit?

Metrics

Posted Jul 31, 2017 13:42 UTC (Mon) by corbet (editor, #1) [Link]

As far as I've been able to tell, the results that come out of cregit closely match the (simpler) "by lines" metric.

Metrics

Posted Aug 1, 2017 16:21 UTC (Tue) by andy_shev (subscriber, #75870) [Link]

Probably I didn't put it clear, I meant independent "modules / drivers" under "files", and statistics here is "by changesets".

$ gt4tree.sh v4.12..origin/master
Christoph Hellwig (246):
Mauro Carvalho Chehab (169):
Thomas Gleixner (143):
Takashi Iwai (130):
Chris Wilson (126):
Arvind Yadav (122):
...

See the last name in the list, here. While I appreciate the work done by Arvind, it's still a mechanical routine which can be easily scripted (coccinelle, sed, etc).