From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Junio C Hamano" <gitster@pobox.com>, "Sjur Moshagen" <sjurnm@mac.com>
Cc: git@vger.kernel.org
Subject: Re: BUGREPORT: Modified files on a fresh clone on M2 MacBook Pro
Date: Wed, 22 Mar 2023 21:00:13 +0100 [thread overview]
Message-ID: <34c11cee-d73e-4de0-85f1-5ecd5fe54c71@app.fastmail.com> (raw)
In-Reply-To: <xmqq355wegsd.fsf@gitster.g>
On Wed, Mar 22, 2023, at 20:18, Junio C Hamano wrote:
> The attribute file says "assume everything is text unless otherwise
> noted below", which you probably should not lose.
That was to illustrate the issue, not to propose a change. Sorry about
not being clear.
(But it also so happens to be the case that I know very little about
`.gitattributes` :))
On Wed, Mar 22, 2023, at 19:47, Sjur Moshagen wrote:
> I will add this and other missing extensions.
By the way, when I first cloned the repository on commit 357c7cf01950
(text, 2023-03-21), those two binary `txt` files showed up as dirty for
me (before you removed them in 6b0acd78f9c9 (Remove accidentally added
files with uncomprehensible content, 2023-03-22)). I guess it was the
same for you.
--
Kristoffer Haugsbakk
next prev parent reply other threads:[~2023-03-22 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 16:28 BUGREPORT: Modified files on a fresh clone on M2 MacBook Pro Sjur Moshagen
2023-03-22 16:46 ` Emily Shaffer
2023-03-22 17:29 ` Sjur Moshagen
2023-03-22 18:22 ` Kristoffer Haugsbakk
2023-03-22 18:47 ` Sjur Moshagen
2023-03-22 19:18 ` Junio C Hamano
2023-03-22 20:00 ` Kristoffer Haugsbakk [this message]
2023-03-22 21:09 ` Sjur Moshagen
2023-03-22 17:33 ` Jeff King
2023-03-22 17:44 ` Jeff King
2023-03-23 5:31 ` Torsten Bögershausen
2023-03-24 4:45 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=34c11cee-d73e-4de0-85f1-5ecd5fe54c71@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sjurnm@mac.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).