Maxim>I would say it doesn't really matter what option is set on build server
It does. You can try with https://github.com/apache/jmeter if you change core.autocrlf between input and true it would checkout text files as LF or CRLF. Maxim>I usually recommend to create per-repo .gitattributes file to avoid different behavior Thanks for the fast response. However .gitattributes is NOT able to specify that. It is related, yet very different. Just in case: .gitattributes allows to specify which files are "text" and which are "binary" .gitattributes allows to enforce line endings for certain files (e.g. it could specify that *.bat should be converted to CRLF always) However, .gitattributes can NOT enforce "platform-native" line endings. You can specify "this file must be LF", you can specify "this file must be CRLF", however you cannot specify that "this file must be LF in macOS and CRLF in Windows". It is core.autocrlf setting that makes Git to convert "text" files with "unspecified eol" to CRLF in Windows. Vladimir
