Re: BUGREPORT: Modified files on a fresh clone on M2 MacBook Pro

From: Sjur Moshagen <sjurnm@mac.com>
Date: Mar 22, 2023, 17:29 UTC
Message-ID: <3FC6072C-5856-437F-9B4F-BC182921426D@mac.com>
In-Reply-To: <CAJoAoZkKTGzgVyL2wM9a4VcFObx4YpjMSatH9Bpqcgyi=zzBrQ@mail.gmail.com>

22.3.2023 kl. 17:46 skrev Emily Shaffer <nasamuffin@google.com>:

Show 18 quoted lines

> 
> On Wed, Mar 22, 2023 at 9:38 AM Sjur Moshagen <sjurnm@mac.com> wrote:
>> 
>> Thank you for filling out a Git bug report!
>> Please answer the following questions to help us understand your issue.
>> 
>> What did you do before the bug happened? (Steps to reproduce your issue)
>> git clone https://github.com/giellalt/lang-sma
>> 
>> What did you expect to happen? (Expected behavior)
>> Clone to be clean, as reported by git status
>> 
>> What happened instead? (Actual behavior)
>> git status reported four changed files
> 
> It would help to know which files, or what the difference was, so we
> have a chance to figure out what happens without having to go and buy
> a Macbook :)

Yes, of course :)

It only happens with binary files (.docx and .pdf files), which got me suspicious. It turned out that updating the .gitattributes file fixed the issue, cf

https://github.com/giellalt/lang-sma/commit/fb5b56fa9fa7f25be1a1d7190bbb4d12b5a908fd#diff-618cd5b83d62060ba3d027e314a21ceaf75d36067ff820db126642944145393e

What is still a mystery to me is that there has been no issues with cloning files on Intel Macs (git version 2.39.2), or on Linux (git version 2.34.1), even with the old .gitattributes file - ie the cloned repos were clean on these systems. Only on M2 (possibly also M1) Macs did this issue pop up.

Please tell me if there is more I can do to help.

Regards, Sjur