> > The only reason to ever support 'lf' is > if you're a total moron of a SCM, and you save files you know are text in > CRLF format internally. That's just f*cking stupid. > What if: - The entire history of the file is stored in CRLF - It's a windows-only file where the official "tool" that reads it barfs on LF line endings. - Third party tools also expect (or at least, handle) CRLF line endings. Even if you end up deciding to store it with LF line endings internally, it should still be *always* checked out with CRLF endings. And no, just because I want certain files to be checked out with CRLF endings, doesn't mean that I want all files to be checked out that way. This is one of the areas where git's crlf handling is lacking right now. Also, git-diff should ignore eol differences by default, unless explicitly asked not to (currently it's the other way around). -- 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