Revert all modified files in an SVN repo

svn status | grep "^M" | while read entry; do file=`echo $entry | awk '{print $2}'`; echo $file; svn revert $file; done
This command allows you to revert every modified file one-by-one in a while loop, but also after "echo $file;" you can do any sort of processing you might want to add before the revert happens.
Sample Output
Reverted 'my/files.txt'

By: wsams
2012-06-17 16:01:06

3 Alternatives + Submit Alt

What Others Think

...or instead of hacking things up with pipes and stuff you could simply use git: git checkout -f master
noqqe · 529 weeks and 6 days ago
Why do people forget that awk has it's own regex filtering capabilities? Anytime you see grep, awk, sed, perl, cut (and a few others) piping into each other, then it's likely able to be improved. In this case: svn st | awk '/^M/ {print $2}' | xargs svn revert
wam · 529 weeks and 4 days ago
I think both of your comments are nice, but we're not forgetting - we're just showing options here on cmdlnfu.
wsams · 529 weeks and 4 days ago
Older versions of awk had some annoying limitations which may explain the habit of reaching for grep, cut, sed first. According to 'The AWK Programming Language' the limits of AWK are: 100 fields 3000 characters per input record 1024 characters per field 15 open files 1 pipe
zlemini · 529 weeks ago
won't "svn revert -R" work?
unixmonkey37567 · 526 weeks and 3 days ago
Oh that's pretty cool, sometimes I want to do work on all newly added files. Like add a license statement to the top and commit each, but not the entire working copy. svn status | grep "^A" | while read entry; do file=`echo $entry | awk '{print $2}'`; echo $file; sed -i '1i MY LICENSE AUTHOR 2012' $file; svn commit $file -m "Adding $file"; done
liamecaps · 526 weeks and 3 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: