From: Kristoffer Haugsbakk Date: Thu, 04 Dec 2025 08:24:13 GMT Subject: Re: diff: should warn about EOL when --no-index ? Message-ID: In-Reply-To: <20251203195424.GB13919@tb-raspi4> On Wed, Dec 3, 2025, at 20:54, Torsten Bögershausen wrote: > On Wed, Dec 03, 2025 at 05:26:49PM +0100, Kristoffer Haugsbakk wrote: >>[[snip] >> > > Not being an expert in `git diff --no-index`: > It seems as if Git reads the .gitconfig and possible .gitattributes here ? Yes it has to do with my config or defaults. That doesn’t matter to the question. > Or what exact setup do yoe use, what is the value for > core.autocrlf > and do you have a .gitattributes file ? > Thinking about it: The warning may be not needed. > On the other hand: It seems as if something in your repo is > not as it should be ? It’s outside a Git repo. > Because the repo should be normalized ? > And if it was, there would be no warning ? > > What does > git ls-files --eol > give you ? > > More information is welcome The warning could be about normalizing the other way for that matter. I’m asking whether the warning should be there in this case. I certainly don’t want to subject people to iteratively guess what my config is like.