From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "Torsten Bögershausen" <tboegi@web•de>
Cc: git@vger•kernel.org
Subject: Re: diff: should warn about EOL when --no-index ?
Date: Thu, 04 Dec 2025 09:24:13 +0100 [thread overview]
Message-ID: <c3aeed96-01e2-4572-80a8-a9eef0cd1315@app.fastmail.com> (raw)
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.
next prev parent reply other threads:[~2025-12-04 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 16:26 diff: should warn about EOL when --no-index ? Kristoffer Haugsbakk
2025-12-03 19:54 ` Torsten Bögershausen
2025-12-04 8:24 ` Kristoffer Haugsbakk [this message]
2025-12-03 22:06 ` 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=c3aeed96-01e2-4572-80a8-a9eef0cd1315@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=tboegi@web$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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