Re: [PATCH/RFC 0/3] Per-repository end-of-line normalization

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: May 7, 2010, 23:50 UTC
Message-ID: <alpine.LFD.2.00.1005071648400.901@i5.linux-foundation.org>
In-Reply-To: <q2y600158c31005071647i80871db0z7a55ae77e738d0d4@mail.gmail.com>

On Fri, 7 May 2010, hasen j wrote:

Show 12 quoted lines

> >
> > The only reason to ever support 'lf' is
> > if you're a total moron of a SCM, and you save files you know are text in
> > CRLF format internally. That's just f*cking stupid.
> >
> 
> What if:
> 
> - The entire history of the file is stored in CRLF
> - It's a windows-only file where the official "tool" that reads it
> barfs on LF line endings.
> - Third party tools also expect (or at least, handle) CRLF line endings.

Umm. Then it's not text, is it? What you are describing is a binary file that happens to look like text with CRLF.

If it's _text_, then you import it as such, and set crlf=true so that it gets checked out with crlf.

		Linus