From: Junio C Hamano Date: Tue, 08 Jan 2008 07:29:30 GMT Subject: Re: CRLF problems with Git on Win32 Message-ID: <7vejcswzad.fsf@gitster.siamese.dyndns.org> In-Reply-To: <5310CD2F-C3B4-404A-9C2E-1D3084B5CC96@zib.de> Steffen Prohaska writes: > But core.autocrlf = true has a slight danger of data corruption. > AFAIK, git's binary detection checks the first "few" bytes (with > few = 8000). This may be sufficient in most case, but I already > met a file that was wrongly classified. (A File format that > starts with a large ASCII header and has chunks of binary data > attached later.) I presume that's where .gitattributes kicks in. > I like Linus' idea of "warn" or Gregory's "fail". Yeah, that feels like a sensible thing to do. > I'm asking the last question because every Unix developer should > think about the option, too. Neither Unix or Windows are causing > the problem alone. That's the logical conclusion. If you are introducing crlf = warn, that means you are declaring that CRLF should be treated as a disease, and that should apply everywhere, not just on Windows (which some people may consider a disease itself, but that is a separate topic).