git diff --numstat | awk '{if ($1 == "0" && $2 == "0") print $3}' | xargs git checkout HEAD

(Git) Revert files with changed mode, not content

I sometimes (due to mismanagement!) end up with files in a git repo which have had their modes changed, but not their content. This one-liner lets me revert the mode changes, while leaving changed-content files be, so I can commit just the actual changes made.

These Might Interest You

What Others Think

this command checks column 1 twice! Any file where you deleted lines will be reverted too. The second $1 should be $2
gressie · 438 weeks and 6 days ago
Adaption that also works for paths with spaces: git diff --numstat | awk '{if ($1 == "0" && $2 == "0") print }' | cut -c 5- | sed 's%^\(.*\)$%"\1"%' | xargs git checkout HEAD
SlashV · 419 weeks and 2 days ago
For binary files the git diff --numstat output is slightly different. For those you have to use: git diff --numstat | awk '{if ($1 == "-" && $2 == "-") print $3}' | xargs git checkout HEAD
theduke · 310 weeks and 5 days ago
To deal with binary files when you have modified ones, this command performs better git diff --stat=1000,1000 | grep -v "bytes$" | sed -rn 's/\s*//;s/\s*\| Bin//p'
alexey_pelykh · 269 weeks and 4 days ago
Fixed one, still has issues with whitespaces in filenames git diff --stat=1000,1000 | grep "| Bin" | grep -v "bytes$" | sed -rn 's/\s*//;s/\s*\| Bin//p' | xargs git checkout HEAD
alexey_pelykh · 269 weeks and 4 days ago
Fixed one, still has issues with whitespaces in filenames git diff --stat=1000,1000 | grep "| Bin" | grep -v "bytes$" | sed -rn 's/\s*//;s/\s*\| Bin//p' | xargs git checkout HEAD
alexey_pelykh · 269 weeks and 4 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?

commandlinefu.com 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.

» 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: