Git rm -- Git add-A after cached changes permission of the file

Asked 2 years ago, Updated 2 years ago, 40 views

I'm going to send you a file.

 git rm -- cached text.php

After removing it from the stage as ,

git add-A

as

git diff 

If so,

old mode 100644
new mode 100755

he said.Go through a lot of things

 [core]
filemode=false

I understand that if you add to config, the permission changes will be ignored, but I don't know the fundamental reason, so I would like you to tell me about the following two things.

なぜWhy do you delete it from the stage → If you upload it to the stage again, the permission will change
②If you look at the file itself in ls-l even though the permission has changed to 644→755, you can see that the permission is -rw-r--r--, not 755
③With git diff

old mode 100644
 new mode 100755

I want to delete what says

Thank you for your cooperation.

[Environment]
Guest machine: Run centOS 6.6 in vagrant.
host machines:macOS
In , the contents of the vagrant are fiddled with phpstorm from macOS (without vagrant ssh).

git

2022-09-29 20:27

1 Answers

I experienced the same phenomenon and solved it in the same way.
After all,
Files referenced, modified, or created from Windows and
Because the permissions of files referenced, modified, or created from Linux are different,
If you commit a file created in the Windows editor, the repository will be your permission.
If you have committed a file created on Linux (abbreviated

)

I think it means that

if you're playing with git at local and cygwin. Files edited in windows will be 644 and will be 755 when committed in cygwin
Clone with cygwin and > because it is different from Windows standard permissions when viewed with windows.
If you commit in windows and git commit-a in cygwin, the file mode will be changed
That's right.

Sorry for not explaining well.


2022-09-29 20:27

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.