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

From: Avery Pennarun <apenwarr@gmail.com>
Date: May 8, 2010, 03:34 UTC
Message-ID: <n2g32541b131005072034o2bceb6b7h34f68ad5c867eddf@mail.gmail.com>
In-Reply-To: <alpine.LFD.2.00.1005071847100.901@i5.linux-foundation.org>

On Fri, May 7, 2010 at 9:49 PM, Linus Torvalds <torvalds@linux-foundation.org> wrote:

Show 7 quoted lines

> 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.

I guess there's your use case for being able to turn off crlf=input, then. :)

Hasen: you and Linus don't seem to be communicating clearly, but it
looks to me like Linus's proposed changes would work fine for your use
case.  What you want is for the repository maintainer to be able to
control whether a file is checked out with crlf or not; this is
possible with *either* a per-project .gitconfig or a crlf=true
attribute that works when core.autocrlf is unspecified, which are
Linus's two suggested options.  If you really, truly want your crlf
characters not to be messed with, then set crlf=false, which means
"binary." [1].

[1] Which reminds me of my opinion about it being too hard to tell what you're specifying given the current set of config options. But 'man gitattributes' makes at least this point clear.

Have fun,

Avery