On Mon, Feb 14, 2011 at 1:36 AM, Tekkub <[email protected]> wrote: > Avery, it sounds like you have a direct line to the git devs, my suggestion > is that git automatically use true on windows and input on everything else > unless the user specifically overrides the autocrlf setting. Right now it > defaults to false if it isn't set. It's very rare for the line endings to > truly matter (i.e. a windows program imploding if it receives LF, like, say, > notepad)... so it's probably best to use smart defaults and let the user > disable it if it's a problem on a case by case basis.
Actually I just read their mailing list sometimes. :) I can't claim to have any real influence here. This is the discussion I found most enlightening if you want the gory details: http://git.661346.n2.nabble.com/What-should-be-the-CRLF-policy-when-win-Linux-tt5008066.html The crlf issues and proposed solutions are rather mind bogglingly complex, which I guess shouldn't be terribly surprising since nobody has solved them during the entire history of computing. Recent versions of git (1.7.x and higher?), if I understand correctly, have new and improved default crlf behaviour that's a bit more desirable than the old behaviour. The bad news is that any change to the default behaviour could mean a whole lot of confused users upon upgrading. Lately I've managed to avoid doing any Windows development; this has made me a happier person on multiple levels, but it also means I don't know what the latest story is on this topic. Hope this helps. Avery -- You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/github?hl=en.
