On Mon, 7 Jan 2008, Robin Rosenberg wrote: > > Indeed, but the most common SCM's detect binary files automatically, > either by suffix or content analysis, so I think that is what user's expect. > It will be right for more projects that the current behaviour. Yeah, I suspect it's not only the "expected" behavior, but people have had years of getting used to the whole binary issue, and are much more likely to expect binary corruption than to expect to have to worry about CRLF. And while it's true that it probably doesn't matter at all as long as you stay windows-only (and everything is CRLF), it's also true that (a) maybe you don't necessarily even know that some day you might want to cast off the shackles of MS and (b) even under Windows you do end up having some strange tools end up using LF (ie you may be using some tools that were just straight ports from Unix, and that write just LF). So defaulting to (or asking) "autocrlf" at install time is probably the safest thing, and then people can edit their global .gitconfig to turn it off. Linus - 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
