Re: diff: should warn about EOL when --no-index ?

From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Dec 4, 2025, 08:24 UTC
Message-ID: <c3aeed96-01e2-4572-80a8-a9eef0cd1315@app.fastmail.com>
In-Reply-To: <20251203195424.GB13919@tb-raspi4>

On Wed, Dec 3, 2025, at 20:54, Torsten Bögershausen wrote:

Show 6 quoted lines

> 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.

Show 6 quoted lines

> 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.

Show 8 quoted lines

> 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.