Why does git flag files as changed when only the line endings are changed and normalization is on?

Question

Case1: windows core.autocrlf=true when I change the line endings of a text file to lf these are marked as changes. But they are all normalized when committed so there shouldn't be any changes.

Case2: linux core.autocrlf=input when I change the line endings of a text file to crlf these are marked as changes. But they are all normalized when committed so there shouldn't be any changes.

So why does git flag files as changed when only the line endings are changed and normalization is on?

score 0 · Answer 1 · answered Jul 25 '16 at 14:43

0

From the git documentation regarding autocrlf:

Git can handle this by auto-converting CRLF line endings into LF when you add a file to the index, and vice versa when it checks out code onto your filesystem.

This is what it the option does, in a nutshell. It does not pervade every single operation of git, only git add and git checkout (and similar, i.e., git reset and probably others that change your working directory).

You might want to look into the text attribute in .gitattributes; maybe that's closer to what you need.

answered Jul 25 '16 at 14:43

AnoE

8,048
1
21
36

what i need is a way commit the line endings that i want without 'changes/conflicts' and checkout with line endings specified in a config file. – Henry Hoendervangers Jul 25 '16 at 14:58
I'd suggest you try `.gitattributes => text`, it will probably do what you want. – AnoE Jul 25 '16 at 15:01

Why does git flag files as changed when only the line endings are changed and normalization is on?

1 Answers1