Get each users commit amount

svn log 2>&1 | egrep '^r[0-9]+' | cut -d "|" -f2 | sort | uniq -c

By: cicatriz
2010-09-06 15:13:48

What Others Think

Heh, neat, you could also do a svn blame count, to see how many lines were changed by each user. Here's the command for a single file: svn blame ANY_FILENAME 2>&1 | awk '{print $2}' | sort | uniq -c ...or if you have a lot of free time on your hands, and want to do a svn blame count on all the files in the current directory branch: svn list -R | sed '/\/$/ d' | xargs echo | xargs svn blame | awk '{print $2}' | sort | uniq -c ...removing "-R" from the previous command will just process the current directory, and will not delve into any subdirs
ArtBIT · 623 weeks ago
Thanks ArtBIT, that's really useful.
cicatriz · 622 weeks and 5 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: