From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: "Sjur Moshagen" <sjurnm@mac.com>,
"Emily Shaffer" <nasamuffin@google.com>,
git@vger.kernel.org
Subject: Re: BUGREPORT: Modified files on a fresh clone on M2 MacBook Pro
Date: Wed, 22 Mar 2023 12:18:26 -0700 [thread overview]
Message-ID: <xmqq355wegsd.fsf@gitster.g> (raw)
In-Reply-To: <73af529d-e918-445d-b0ee-9506e28188af@app.fastmail.com> (Kristoffer Haugsbakk's message of "Wed, 22 Mar 2023 19:22:09 +0100")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> modified: "corp/Sn\303\245sningen 2013/50 uke/Dramatikk og kj\303\246rlighet - S\303\270rsamisk.doc"
>
> no changes added to commit (use "git add" and/or "git commit -a")
>
> Note that this `doc` extension was not covered by your update.
>
> But it becomes clean if I remove this line:
>
> $ git diff
> diff --git a/.gitattributes b/.gitattributes
> index bbd8c0db810d..3959fefadfc1 100644
> --- a/.gitattributes
> +++ b/.gitattributes
> @@ -2,7 +2,6 @@
> # DO NOT EDIT - the file is updated via the template system.
>
> # Some defaults:
> -* text eol=lf
> *.png binary
> *.jpg binary
> *.jpeg binary
The attribute file says "assume everything is text unless otherwise
noted below", which you probably should not lose. Instead, I would
declare *.doc are also binary by appending a new entry at the end of
the file, if I were managing that project.
next prev parent reply other threads:[~2023-03-22 19:18 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 [this message]
2023-03-22 20:00 ` Kristoffer Haugsbakk
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=xmqq355wegsd.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=nasamuffin@google.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).