Re: Odd Difference Between Windows Git and Standard Git

From: Jon Forrest <nobozo@gmail.com>
Date: May 20, 2016, 13:48 UTC
Message-ID: <c20b9819-1b2d-6704-d870-1c0102dd9e35@gmail.com>
In-Reply-To: <c07df4ac-08c9-8eaa-0233-06616945c857@web.de>

On 5/20/2016 6:19 AM, Torsten Bögershausen wrote:

Show 16 quoted lines

> On 20.05.16 03:48, Jon Forrest wrote:
>> I'm running Git version 2.8.2 built from source on Ubuntu 16.04.
>> I'm using a repository that's stored on Dropbox. I'm the only person
>> accessing this repo. Everything works great.
>>
>> For reasons unrelated to Git, I decided to try Git for Windows,
>> so I installed "git version 2.8.2.windows.1" on Windows 10.
>> When I run 'git status' on Ubuntu the list I see is exactly what
>> I expect. However, when I run 'git status' on the
>> same Dropbox repo on Windows, I see what I expect plus I'm told
>> that every .pdf file and some .png files are modified.
> To bring at least a little light into the story:
>
> What does
> git diff
> say ?

Great question. For all the unexpected files it says the same thing:

old mode 100755 new mode 100644

> What does
> git config -l | grep core
> say ?

core.symlinks=false core.autocrlf=true core.fscache=true core.editor=vim core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true

>
> And what does
> git ls-files --eol
> say?

The same thing for all the unexpected files, which is:

i/-text w/-text attr/

I'm running the above commands on Windows.

The result of the 2nd question on Ubuntu is:

core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true

and the 3rd (for the expected files) is:

i/lf    w/lf    attr/

Jon