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

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: May 8, 2010, 01:49 UTC
Message-ID: <alpine.LFD.2.00.1005071847100.901@i5.linux-foundation.org>
In-Reply-To: <i2g600158c31005071839wc5269ffqc88cb26e48c44748@mail.gmail.com>

On Fri, 7 May 2010, hasen j wrote:

Show 9 quoted lines

> > However, if you think that it needs to be CRLF on _all_ platforms, even
> > platforms where CRLF is _wrong_ for a text-file, then see above: in that
> > case it's not a text-file at all as far as the SCM is concerned.
> >
> > In that case it's just a binary file, and CRLF is _not_ "end of text
> > line", it's part of the definition of the format for that binary file.
> 
> What does the platform care? This doesn't make any sense. Files that
> need CRLF are not Unix files to begin with (e.g. sln).

Don't be silly.

The whole AND ONLY point of CRLF translation is that line-endings are different on different platforms.

So when you say "What does the platform care?", that is a totally idiotic and utterly stupid thing to ask.

And since you ask it, I can only assume that you don't understand anything about the whole CRLF discussion, that you don't care about cross-platform repositories, and that as a result you should NEVER EVER actually use any of the git crlf conversion code.

It's that simple. You seem to totally miss the whole point of the whole feature in the first place.

			Linus