Re: CRLF problems with Git on Win32

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 8, 2008, 10:35 UTC
Message-ID: <7v4pdovc4e.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <20080108100818.GA17205@coredump.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 6 quoted lines

> On Mon, Jan 07, 2008 at 11:29:30PM -0800, Junio C Hamano wrote:
>
>> Steffen Prohaska <prohaska-wjoc1KHpMeg@public.gmane.org> writes:
>
> I'm not sure what's causing it, but all of the addresses in your message
> (including cc headers) got munged.

I think Steffen's original got munged (I just replied to it) by gmane's mail relaying interface.

Show 13 quoted lines

>> > 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).
>
> It's unclear to me: is such a warning only supposed to happen when we
> see CRLF _after_ we have determined that a file is not actually binary?

Oh, I agree.  I thought that was what Steffen was proposing.