I'm new to git, and I've read a lot about line endings and
how git treats them. I'm on Windows by the way. I have made
a .gitattributes
file and set for example *.txt to text.
When I commit a .txt file, I get the warning:
warning: CRLF will be replaced by LF in whatever.txt
But I know that. I don't need that warning. Replacing line
endings in text files is what I want.
Now, setting safecrlf
to false makes the warning
disappear, but the manual for safecrlf
reads:
If true, makes git check if converting CRLF is reversible
when end-of-line conversion is active. Git will verify if
a command modifies a file in the work tree either directly
or indirectly. For example, committing a file followed by
checking out the same file should yield the original file
in the work tree. If this is not the case for the current
setting of core.autocrlf, git will reject the file.
From that, safecrlf
seems like a good idea to have.
However, I don't understand why setting safecrlf
to true
gives me warnings about my text files; it seems to me that
those are different issues -- the warning on text files and
the checking if reversible. Indeed, git does not reject my
file.
Can I get rid of the warnings for text files, and still have
safecrlf
set? Or am I misunderstanding something?
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…