On 7 May 2010 19:49, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > > > On Fri, 7 May 2010, hasen j wrote: >> > However, if you think that it needs to be CRLF on _all_ platforms, even >> > platforms where CRLF is _wrong_ for a text-file, then see above: in that >> > case it's not a text-file at all as far as the SCM is concerned. >> > >> > In that case it's just a binary file, and CRLF is _not_ "end of text >> > line", it's part of the definition of the format for that binary file. >> >> What does the platform care? This doesn't make any sense. Files that >> need CRLF are not Unix files to begin with (e.g. sln). > > Don't be silly. > > The whole AND ONLY point of CRLF translation is that line-endings are > different on different platforms. > > So when you say "What does the platform care?", that is a totally idiotic > and utterly stupid thing to ask. > > And since you ask it, I can only assume that you don't understand anything > about the whole CRLF discussion, that you don't care about cross-platform > repositories, and that as a result you should NEVER EVER actually use any > of the git crlf conversion code. > > It's that simple. You seem to totally miss the whole point of the whole > feature in the first place. > > Linus > I worked on several projects on windows where ALL my files were LF; the platform didn't give a shit and everything worked great. I don't suppose you use the CRLF feature yourself, not to mention doing any windows development (ever?). The way git handles crlf is just confusing; in fact it's so confusing that it's often better to just turn it off. I'm not the only person who thinks that. It's specifically confusing because git thinks "if you're on windows then ALL your files should be CRLF", which is clearly what you think. The platform is not windows, it's the development tools. Most development tools don't actually mind if the line endings are LF only, and since CRLF conversions in git cause endless confusion, it's better to turn it off most of the time, unless you're dealing with a retarded tool that think CRLF is the only line ending and fails to read files with LF endings. When that happens, it's most likely the case that these files are platform-dependent anyway, and so converting them back and forth between LF and CRLF is just a waste of time. The whole idea behind my suggestion is to minimize confusion. -- 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