> Anyway, BY DEFAULT it is off regardless, because it requires a > > [core] > AutoCRLF = true > > in your config file to be enabled. We could make that the default for > Windows, of course, the same way we do some other things (filemode etc). This whole auto CRLF things seems to deal with DOS issues that I personally have not encountered since looong time ago. Granted notepad in Windows does not understand UNIX files but that a bug in notepad and everyone knows that wordpad can be used. I wonder what we are really trying to address here. Or in other words could the original poster maybe tell what Windows IDE's that does not handle UNIX files properly? core git today should not care about CRLF as opposed to LF end-of-line as long as the end-of-line is consistent - correct? So defaulting to autoCRLF in Windows/DOS environments was maybe sane 10 years ago but today that seems to be the wrong thing to do. For certain project the option could be useful if the tool-set in the project *requires* CRLF, but if the toolset like all modern toolset supports both CRLF and LF then git better avoid changing end-of-line marker. Sam - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html