Getting rid of "mode change" on cygwin

Maaartin· Sep 24, 2010, 18:57 UTC · lore

I just switched from svn to git and in my first git commit all files get status modified with

mode change 100644 => 100755

I don't care about the file mode much, the 755 mode makes no sense but is probably some cygwin magic, as it may be hard to emulate the perms, so it simply considers all files as executables. I can't change the mode, since chmod a-x does nothing at all. Actually, I don't care about the perms at all, I'd be happy if git would show "no change" for unchanged files.

Andreas Schwab· Sep 24, 2010, 19:36 UTC · re: Maaartin · lore

Re: Getting rid of "mode change" on cygwin

Maaartin <grajcar1@seznam.cz> writes:

Show 10 quoted lines

> I just switched from svn to git and in my first git commit all files get status 
> modified with
>
> mode change 100644 => 100755
>
> I don't care about the file mode much, the 755 mode makes no sense but is 
> probably some cygwin magic, as it may be hard to emulate the perms, so it simply 
> considers all files as executables. I can't change the mode, since chmod a-x 
> does nothing at all. Actually, I don't care about the perms at all, I'd be happy 
> if git would show "no change" for unchanged files.

$ git config core.filemode false

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."