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.

UpGuard checks and validates configurations for every major OS, network device, and cloud provider.

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



fetch all revisions of a specific file in an SVN repository

Terminal - fetch all revisions of a specific file in an SVN repository
svn log fileName|cut -d" " -f 1|grep -e "^r[0-9]\{1,\}$"|awk {'sub(/^r/,"",$1);print "svn cat [email protected]"$1" > /tmp/fileName.r"$1'}|sh
2009-05-27 02:11:58
User: fizz
Functions: awk cut grep
fetch all revisions of a specific file in an SVN repository

exported files will get a .r23 extension (where 23 is the revision number)


There are 2 alternatives - vote for the best!

Terminal - Alternatives
svn log fileName | sed -ne "/^r\([0-9][0-9]*\).*/{;s//\1/;s/.*/svn cat [email protected]& > fileName.r&/p;}" | sh -s
2009-09-04 17:23:45
User: arcege
Functions: sed sh
Tags: svn sed shell

Manages everything through one sed script instead of pipes of greps and awks. Quoting of shell variables is generally easier within a sed script.

Know a better way?

If you can do better, submit your command here.

What others think

Why would anyone want to do this?

Comment by wonko 459 weeks and 3 days ago

finding a specific revision where you had a specific piece of code.

I'd love to hear about any better way to search my repo without any 3rd party tools

Comment by fizz 459 weeks and 3 days ago

I don't use SVN so I don't know the specific command. If you're looking to find which revision added a line that is in the current revision you probably want to use svn annotate. That should give you the revision the line was added and you can call that one right up.

If you're looking for lines of code that don't exist in the current revision, I can't help you with that. There very well might be a command, but that isn't something I've ever had the need to do with any RCS I've ever used.

Comment by wonko 459 weeks and 2 days ago

wonko is right to mention svn annotate, or as I prefer it, svn blame. If you're using KDE, kdesvn, a Konqueror-integrated SVN client is a handy tool that I use from time to time when I really need to dig into subversion history and the command line gets a little tiring. Great command!

Comment by bwoodacre 459 weeks and 2 days ago

Your point of view

You must be signed in to comment.