Hi David and Junio. At first, I was planning to reply that I'd probably not be qualified for that. But to tell the truth, I have been writing a lot of CR/LF/CRLF code throughout the years, so maybe I could do it. Unfortunately, I have to go slow about programming, because I burned myself out a number of times, so programming "work" is not compatible with me; though programming "hobby" is. The implementation would be dependent on on how git is currently handling lines. Worst case is, if it's mixed CR, LF and CRLF, such as a text-file, that contains all 3 kinds of line endings (because 3 different people have been editing the file). Love Jens On Wed, 26 Sep 2012 01:42:02 -0700, David Aguilar wrote: > 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