As I understand, default value unix was chosen to avoid problems on unix systems.
Which works well for everyone from Unix, but for Windows users it might be just confusing.
Just as CRLF can create problems on Unix, LF can create problems on Windows.
Nowadays, git for Windows by default has core.autocrlf=true - meaning git automatically converts files to CRLF just for local use, but CRLF not commited to repo and repo still stores them as LF.
So files on Windows are typically CRLF, which helps avoid problems, but doesn't create a headache for anyone else on the repo, because repo line-ending format is defined separately
And Windows user would try to accomodate unix new-lines type, then they might end up fighting against autocrlf and there wouldn't be any benefit from this.
The proposal is to switch default type to platform.
As I understand, default value
unixwas chosen to avoid problems on unix systems.Which works well for everyone from Unix, but for Windows users it might be just confusing.
Just as
CRLFcan create problems on Unix,LFcan create problems on Windows.Nowadays, git for Windows by default has
core.autocrlf=true- meaning git automatically converts files toCRLFjust for local use, butCRLFnot commited to repo and repo still stores them asLF.So files on Windows are typically
CRLF, which helps avoid problems, but doesn't create a headache for anyone else on the repo, because repo line-ending format is defined separatelyAnd Windows user would try to accomodate
unixnew-linestype, then they might end up fighting againstautocrlfand there wouldn't be any benefit from this.The proposal is to switch default type to
platform.