Git script to measure contributor LOCs

and for mercurial<p><a href="http://mercurial.selenic.com/wiki/ChurnExtension" rel="nofollow">http://mercurial.selenic.com/wiki/ChurnExtension</a><p>user LOC<p><pre><code> $ hg churn -t users@email 30454 **************************************************** </code></pre> users' changesets<p><pre><code> $ hg churn -c user1 65 **************************************************** user2 41 ********************************* user3 2 **</code></pre>

For those of us not on BSD:<p><pre><code> git ls-files -z | xargs -0 -n1 -E'\n' git blame --date short -wCMcp | perl -pe 's/^.*?\((.*?) +\d{4}-\d{2}-\d{2} +\d+\).*/\1/' | sort | uniq -c | sort -rn</code></pre>

Is LOC still a worthwhile metric to estimate developer productivity?

git blame -p is going to be easier to parse<p>example:<p><pre><code> git blame --line-porcelain |awk 'BEGIN { ORS=" " } $1=="author" {for (i=2;i&#60;=NF;++i) print $i; printf("\n")}'|sort|uniq -c|sort -n </code></pre> better:<p><pre><code> git ls-files -z|xargs -0 -n1 git blame --line-porcelain|awk '$1=="author" {auth=$2; for(i=3;i&#60;=NF;++i) auth=auth " "$i; counts[auth]+=1} END {for(a in counts) print counts[a],a}'</code></pre>

Much more extensive and detailed information is provided by <a href="https://github.com/hoxu/gitstats" rel="nofollow">https://github.com/hoxu/gitstats</a>

Very cool -- thanks for sharing.