What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. 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.

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Universal configuration monitoring and system of record for IT.

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.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

gets all files committed to svn by a particular user since a particular date

Terminal - gets all files committed to svn by a particular user since a particular date
svn log -v -r{2009-05-21}:HEAD | awk '/^r[0-9]+ / {user=$3} /yms_web/ {if (user=="george") {print $2}}' | sort | uniq
2009-06-05 14:07:28
User: jemptymethod
Functions: awk sort
gets all files committed to svn by a particular user since a particular date

just change the date following the -r flag, and/or the user name in the user== conditional statement, and substitute yms_web with the name of your module


There are 4 alternatives - vote for the best!

Terminal - Alternatives
svn log -v -r{2009-11-1}:HEAD | awk '/^r[0-9]+ / {user=$3} /./{if (user=="george") {print}}' | grep -E "^ M|^ G|^ A|^ D|^ C|^ U" | awk '{print $2}' | sort | uniq
2011-12-05 07:36:44
User: smilyface
Functions: awk grep sort
Tags: svn awk log

svn log -v --> takes log of all



-r {from}{to} --> gives from and to revision



awk of line 'r'with numbers

Assign user=3rd column [ie; username]



if username = George

print details



Print lines starts with M/U/G/C/A/D

[* A Added * D Deleted * U Updated * G Merged * C Conflicted]



sort all files



Print only uniq file's name alone.

Know a better way?

If you can do better, submit your command here.

What others think

OMG! Thanks man, for this peace of heaven. This command save my life (ok, but save hours of work).


Comment by lawrence 372 weeks and 1 day ago

Here is a shell for this. I just made for my usage. May be helpful for u too. The before told command itself i used , but with details of commit also included.

Do as follows.

create a file

vi svn_get_user_committed_files_details.sh

press i

then copy & paste the following as it is. And then make the shell executable with the command chmod.

[Don't forget to change PROJECT path. :)]







[ -f $svnfile_log_all ] && rm -f $svnfile_log_all

[ -f $svnListUNames ] && rm -f $svnListUNames

[ -f $svnUserCommitted ] && rm -f $svnUserCommitted

echo -e "\nPlease wait..\n"

svn log -v $PROJECT > $svnfile_log_all

if [ -z $uName ]; then

cat $svnfile_log_all | awk -v uName=$uName '/^r[0-9]+ / {user=$3} /./ {print user} ' | grep -v "^$" |sort | uniq >> $svnListUNames


if [ `cat $svnfile_log_all | grep "$uName" | wc -l` -gt "0" ]; then

echo $uName > $svnListUNames


echo -e "\n>>>>>user: $uName not committed any files.

exit 0



echo -e "\n\nRepo Name: `cat $PROJECT/.svn/entries | grep "

while read uName


echo -e "$uName committed files\n======================" >> $svnUserCommitted

cat $svnfile_log_all | awk -v uName=$uName '/^r[0-9]+ / {user=$3} /./{if (user==uName) {print}}' | grep -E "^ M|^ G|^ A|^ D|^ C|^ U" | awk '{print $2}' | sort >> $svnUserCommitted

echo -e "\n\nIn Detail:\n==========" >> $svnUserCommitted

cat $svnfile_log_all | awk -v uName=$uName '/^r[0-9]+ / {user=$3} /./{if (user==uName) {print}}' >> $svnUserCommitted

echo -e "\n"

done < $svnListUNames

echo -e "Log is in : $svnUserCommitted\n"

cat $svnUserCommitted

Comment by smilyface 252 weeks and 3 days ago

A shell script for doing this kind of defeats the purpose of command line fu

Comment by jemptymethod 252 weeks and 3 days ago

Your point of view

You must be signed in to comment.