On Thu, Sep 13, 2012 at 9:51 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > David Aguilar <davvid@xxxxxxxxx> writes: > >> git doesn't really even support LF. > > At the storage level that is correct, but the above is a bit of > stretch. It may not be "support", but git _does_ rely on LF when > running many text oriented operations (a rough rule of thumb is > "does 'a line' in a file matter to the operation?"). Think about > "git diff" and "git blame". Thanks for the thorough explanation. You're 100% correct, as always. I'll be honest: I had a small bias when responding. I didn't want anyone to think a "autocr" feature would be useful, so I played the "git is really simple" angle hoping it would put a kabosh on the idea. That was a little silly of me. That said, perhaps the "autocrlf" code is simple enough that it could be easily tweaked to also handle this special case, but I am not familiar with the code enough to say. My gut feeling was that it was too narrow a use case. I guess if someone[*] wanted to whip up a patch then it would be a different story, but it doesn't seem to be the itch of anyone around here so far. [*] Jens, that could be you ;-) cheers, -- David -- 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