Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I switch between using tortoise git and cmd line git on cygwin very frequently, and lately I've noticed that when I git status via cygwin and no changes are found, then I go to use tortoise git, and right click on a repo then use the "Git Commit -> ..." menu item, I get a list of files that have supposedly changed, but of course when review the diff there are no changes to the file contents, it's actually the file permissions which appear to be changed, which git via cygwin does not recognize.

So what is wrong with my tortoise git setup?

share|improve this question
1  
What have the permissions changed from and to? – ChrisF May 7 '10 at 10:29
1  
well the mode seems to change back and forth between mode 100644 to 100755, not sure how this corresponds to permissions, I just assumed it is. – erikvold May 8 '10 at 6:51
    
This looks similar, but I don't know how to change the core.filemode to false.. – erikvold May 8 '10 at 13:55
up vote 8 down vote accepted
$ git config core.filemode false

Read the documentation on git config.

add --global to set it over all of your git projects.

share|improve this answer

It appears that TortoiseGit and Git Gui don't handle the x bit on Windows as well as cygwin does. Most people probably don't care about changing the x bit, so "core.filemode false" is a good solution to keep both cygwin and your GUI happy.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .