Running git on a Windows XP machine, using bash. I exported my project from SVN, and then cloned a bare repository.
I then pasted the export into the bare repositori
Most of tools in Windows accepts only LF in text files. For example you can control the behaviour for Visual Studio in a file named '.editorconfig' with following example content (part):
indent_style = space
indent_size = 2
end_of_line = lf <<====
charset = utf-8
Only the original Windows-Notepad does not work with LF but there are some more proper simple editor tools available!
Hence You should use LF in text files in Windows too. This is my message, stronlgy recommended! There is no reason to use CRLF in windows!
(The same discussion is using \ in include paths in C/++, it is bullshit, use #include
Hence the proper setting for git is
git config core.autocrlf false
My message: Forget such old thinking programs as dos2unix and unix2dos. Clarify in your team that LF is proper to use under Windows.