How do I remove files saying old mode 100755 new mode 100644 from unstaged changes in Git

Question

For some reason  when I initially did a pull from the repository for a git project of mine  I got a ton of files in my working copy that have no discernible changes made to them  but keep showing up in my unstaged changes area     I m using Git Gui on Windows xp  and when I go to look at the file to see what has changed  All I see is   old mode 100755   new mode 100644     Does anyone know what this means     How can I get these files out of my list of unstaged changes   Very annoying to have to go through 100 s of files  just to pick out files I ve recently edited and want to commit

User · Answer

You can use the following command to change your file mode back  git add --chmod  x -- filename Then commit to the branch

User · Answer

The accepted answer to set git config core filemode false  works  but with consequences  Setting core filemode to false tells git to ignore any executable bit changes on the filesystem so it won t view this as a change  If you do need to stage an executable bit change for this repository anytime in the future  you would have to do it manually  or set core filemode back to true  A less consequential alternative  if all the modified files should have mode 100755  is to do something like chmod 100755   git ls-files --modified   which just does exactly the change in mode  no more  no less  without additional implications   in my case  it was due to a OneDrive sync with my filesystem on MacOS  by not changing core filemode  I m leaving the possibility open that the mode change might happen again in the future  in my case  I d like to know if it happens again  and changing core filemode will hide it from me  which I don t want

User · Answer

I just ran into this issue when diffing my branch with master  Git returned one  mode  error when I expected my branch to be identical to master  I fixed by deleting the file and then merging master in again   First I ran the diff   git checkout my-branch git diff master   This returned   diff --git a bin script sh b bin script sh old mode 100755 new mode 100644   I then ran the following to fix   rm bin script sh git merge -X theirs master   After this  git diff returned no differences between my-branch and master

User · Answer

You could try git reset --hard HEAD to reset the repo to the expected default state

User · Answer

I have faced the same issue  And this save my life  https   gist github com jtdp 5443498  git diff -p -R --no-color     grep -E    diff  old new  mode   --color never      git apply

User · Answer

This usually happens when the repo is cloned between Windows and Linux Unix machines  Just tell git to ignore filemode change  Here are several ways to do so   Config ONLY for current repo   git config core filemode false   Config globally   git config --global core filemode false   Add in    gitconfig    core        filemode   false    Just select one of them

User · Answer

I had just the one troublesome file with the changed permissions  To roll it back individually  I just deleted it manually with rm  lt file gt  and then did a checkout to pull a fresh copy    Luckily I had not staged it yet    If I had I could have run git reset --  lt file gt  before running git checkout --  lt file gt

User · Answer

Setting core filemode to false does work  but make sure the settings in    gitconfig aren t being overridden by those in  git config

User · Answer

I ve encountered this problem when copying a git repo with working files from an old hard drive a couple times  The problem stems from the fact that the owner and permissions changed from the old drive machine to the new one  The long and short of it is  run the following commands to straighten things out  thanks to this superuser answer    sudo chmod -R -x     remove the executable bit from all files   The former command will actually resolve the differences that git diff reported  but will revoke your ability to list the directories  so ls    fails with ls     Permission denied  To fix that   sudo chmod -R  X     add the executable bit only for directories   The bad news is that if you do have any files you want to keep executable  such as  sh scripts  you ll need to revert those  You can do that with the following command for each file   chmod  x   build sh   where build sh is the file you want to make executable again

User · Answer

This solution will change the git file permissions from 100755 to 100644 and push changes back to the bitbucket remote repo   Take a look at your repo s file permissions  git ls-files --stage  If 100755 and you want 100644   Then run this command  git ls-files --stage   sed  s  t   g    cut -d    -f4   xargs git update-index --chmod -x  Now check your repo s file permissions again  git ls-files --stage  Now commit your changes    git status git commit -m  quot restored proper file permissions quot  git push

User · Answer

It seems you have changed some permissions of the directory  I did the following steps to restore it      git diff  gt  backup-diff txt                    in case you have some other code changes      git checkout

User · Answer

This happens when you pull and all files were executable in the remote repository  Making them executable again will set everything back to normal again   chmod  x  lt yourfile gt    For one file chmod  x folder      For files in a folder   You might need to do   chmod -x  lt file gt     Removes execute bit   instead  for files that was not set as executable and that was changed because of the above operation  There is a better way to do this but this is just a very quick and dirty fix

User · Answer

This worked for me  git ls-files -m   xargs -L 1 chmod 644

User · Answer

That looks like unix file permissions modes to me  755 rwxr-xr-x  644 rw-r--r--  - the old mode included the  x  executable  flag  the new mode doesn t   This msysgit issue s replies suggests setting core filemode to false in order to get rid of the issue   git config core filemode false

[git] How do I remove files saying "old mode 100755 new mode 100644" from unstaged changes in Git?

Examples related to git

Examples related to git-gui