On Mon, May 24, 2010 at 02:22:13PM +0200, Erik Faye-Lund wrote: > > I thought the original motivation behind this change was to make repos > with CRLF-textfiles work without reporting diffs on all lines when > autocrlf was enabled. Because checking in CRLF-files DOES happen, and > for some of us the reality is that we have to deal with such repos. Sure, but then CRLF files are treated as "binary" as far as autocrlf is concerned. There is no conversion for such files even though automatic text detection would detect them as. Thus, you do not have to worry that enabling autocrlf may be incompatible with some repositories. The situation is different when a file explicitly marked by attributes to have some particular ending. It is a policy of that repository, and if it is not followed, it means it is "corrupted". It is similar to what you would have with SVN with eol-style=native for some file while it being stored with CRLF inside of the SVN repository (obviously, any standard SVN client should not allow this to happen). Dmitry -- 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