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

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: May 7, 2010, 19:40 UTC
Message-ID: <alpine.LFD.2.00.1005071235070.901@i5.linux-foundation.org>
In-Reply-To: <alpine.LFD.2.00.1005071529050.14468@xanadu.home>

On Fri, 7 May 2010, Nicolas Pitre wrote:

> 
> Given that only a subset of gitconfig could make sense to have 
> distributed, I think the file should be named .gitparams to make the 
> distinction clear.

I went through the options listed in "man gitconfig", and quite frankly, I didn't find any new ones. I didn't grep the source, and I'm sure they're not all documented, but if it really is just two options, I doubt it's worth it at all.

Hopefully nobody sane uses any non-utf8 encoding for commit messages anyway (but what do I know - I have no idea about Asian usage, where it may make more sense than in US/Western Europe). So i18n.commitEnconfig is not likely to be a big deal.

And just making the crlf attribute work regardless of core.autocrlf sounds like it wouldn't be a bad idea. Just _maybe_ we could actually make an _explicit_ "core.autocrlf = off/false" actually disable any .gitattribute crlf settings, but I'm not sure even that is a good idea.

So I'd suggest relegating "core.autocrlf" to just files that are _not_ covered by some explicit .gitattribute setting. After all, that just more solidly puts the "auto" in autocrlf.

		Linus