> I personally find that autocrlf causes more confusion than it solves problems. > > I've yet to see a text editor on windows that can't handle \n line > endings. (Notepad doesn't count) > > Just keep the project with \n line endings, disable autocrlf, and make > sure that people are aware of this. Editors may handle it gracefully but older Windows programs will have problems. For instance, Visual Studio 6 will barf on Visual Basic projectfiles with non-windows line-style endings. (And please don't ask why I know this....) -- Kind regards, Wilbert van Dolleweerd Blog: http://walkingthestack.blogspot.com/ Twitter: http://www.twitter.com/wvandolleweerd -- 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