From: Jeff King <peff@peff.net>
To: Emily Shaffer <nasamuffin@google.com>
Cc: Sjur Moshagen <sjurnm@mac.com>, git@vger.kernel.org
Subject: Re: BUGREPORT: Modified files on a fresh clone on M2 MacBook Pro
Date: Wed, 22 Mar 2023 13:44:33 -0400 [thread overview]
Message-ID: <20230322174433.GA11532@coredump.intra.peff.net> (raw)
In-Reply-To: <20230322173351.GC4296@coredump.intra.peff.net>
On Wed, Mar 22, 2023 at 01:33:51PM -0400, Jeff King wrote:
> On Wed, Mar 22, 2023 at 09:46:11AM -0700, Emily Shaffer wrote:
>
> > 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 :)
>
> Just a guess, but it probably has to do with Unicode normalization.
Heh. After reading the other response in this thread, I could not have
been further from the truth. :) Sorry for the noise.
-Peff
next prev parent reply other threads:[~2023-03-22 17:45 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
2023-03-22 21:09 ` Sjur Moshagen
2023-03-22 17:33 ` Jeff King
2023-03-22 17:44 ` Jeff King [this message]
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=20230322174433.GA11532@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--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).