>> >> When I'm on windows, I prefer LF (unless the project already uses >> CRLF, or it's outside my control). >> > > "When I'm on windows" leads me to believe Windows is not your primary > operating system. If not, please excuse me. I used to be, I only moved to linux about a year ago, but I use windows at work, and I started using git when I was on windows. > Open source isn't the only model for developing software. But it's probably the most common scenario where people run into line ending issues. If the project is a VS project, then it's probably not multi-platform, plus everyone at the company would be using windows anyway, so there's no line-ending issue. > And again... even if it were, working well together with > visual studio support would be very beneficial for quite a bit of > projects. Visual Studio is probably the most used code-editor among > Windows-developers (with a good margin too, I suspect), so ignoring it > is would just be sticking your head in the sand - or worse, asking for > less contributions from Windows-users (which can often be a problem in > the first place). The problem can be avoided with a little bit of education. VS is not a multiplatform IDE anyway Sure, it can't work with LF endings as well as notepad++, but it's not git's responsibility to try to fix that. I just don't think it's a big enough issue to be built into git. IMHO it's much better to work around the problem (if and when it arises) by using clean and smudge filters in .gitattributes, than having it built in and enabled by default in the msysgit installer. -- 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