Steffen Prohaska <prohaska@xxxxxx> writes: > I believe the main question is which type of projects we would like > to support by our default. For real cross-platform projects that will > be checked out on Windows and Unix we should choose > "core.autocrlf true" as our default. But if our default are native > Windows projects that will never be checked out on Unix, then we > should not set core.autocrlf by default. If the primary target is native Windows projects that wants CRLF in the work tree, you could still set core.autocrlf. Your checkouts will be with CRLF. And someday perhaps somebody may offer porting that to UNIX and his checkout will be without CR. So wouldn't the categorization be more like this? - "real cross-platform" would want core.autocrlf = true; - "native Windows" can work either way; - "originated from UNIX" would be helped with core.autocrlf = true; - 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
