Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > When a file's crlf attribute is explicitely set, it does not make sense > to ignore it, just because the config variable core.autocrlf has not > been set. I am not sure if I agree with that reasoning. Attribute defines what each path is. Is it a text file, is it a binary? The nature of the contents does not change between people on POSIX and Windows, and that is why it is described in .gitattributes and cloned across repositories. On the other hand, the configuration defines what to do with contents with various attributes in this particular repository. Do I want to see a text file checked out with CRLF endings, or LF? So it is perfectly valid and normal for a cross-platform minded project to use the crlf atttribute to say "These files are text" and expect them to be checked out with LF endings on POSIX while making sure they are checked out with CRLF on Windows. Adding CR at the end of line for such files on POSIX systems is positively a wrong thing to do in such a case. Projects like the kernel that originate from LF side of the world may not bother marking things as such, though. -- 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
