On 12/27/2021 3:13 PM, Adam Dinwoodie wrote:
[snip]
This is normal Git behaviour: it doesn't record detailed file
permissions, only presence or absence of an executable bit. It only
ever shows file permissions as 644 (meaning "not executable") or 755
(meaning "executable").
Specifically, the committed version of your .gitignore file is not
executable, but the version in your current working copy is
executable. This is a common side-effect of checking the repository
out using Cygwin's Git, then accessing the repository with native
Windows programs, which includes Git for Windows. Cygwin emulates the
*nix approach of not setting the executable bit unless it's necessary,
whereas native Windows programs almost always set the executable bit
on any file they touch in common with normal Windows application
practice.
If this behaviour is undesirable for you, I'd recommend either
sticking to using Cygwin editors, or running `git config core.fileMode
false` to instruct Git to ignore the executable bit on the filesystem.
Thanks for the detailed explanation, that makes perfect sense.
--
Jim Garrison
j...@acm.org
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
