From: Brian Gernhardt Date: Sun, 02 Sep 2007 16:47:32 GMT Subject: Re: [PATCH] Add a new lstat implementation based on Win32 API, and make stat use that implementation too. Message-ID: In-Reply-To: <3f4fd2640709020933sa2bdec0g532500ea49c179b5@mail.gmail.com> On Sep 2, 2007, at 12:33 PM, Reece Dunn wrote: > You pull a repository that contains executable scripts that are > required to work in order to build the system. You then make some > modifications to the local repository and run the 'git add .' command. > Since this patch is reporting executable bits differently, the mode > change is stored as well as the local modifications. Now the changes > are pushed upstream (along with the file mode changes). > > Someone running a Linux machine, pulls your changes. When those files > are checked out, the executable state of those scripts has now > changed, preventing the Linux user from running those scripts. _That_ > is what I meant. Or am I misunderstanding how git works in this case? This is what "git config core.fileMode false" is for. See git- config's man page for information (or Documentation/config.txt). We already have a way to tell git that the "executable bit" is worthless, and any Windows port should use it. ~~ B