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

From: Avery Pennarun <apenwarr@gmail.com>
Date: May 7, 2010, 21:26 UTC
Message-ID: <x2j32541b131005071426tb875cc1dtcc26e86d868d2e8b@mail.gmail.com>
In-Reply-To: <alpine.LFD.2.00.1005071708090.14468@xanadu.home>

On Fri, May 7, 2010 at 5:12 PM, Nicolas Pitre <nico@fluxnic.net> wrote:

Show 8 quoted lines

> On Fri, 7 May 2010, Avery Pennarun wrote:
>> It has exactly the same syntax as ~/.gitconfig, and the options it
>> does support can all be carried over literally to ~/.gitconfig.
>
> Absolutely not.
>
> Most options for ~/.gitconfig simply make no sense in a distributed
> .gitconfig file.

No, that's the converse of what I said.

Try this in your head:

    cp .gitconfig .git/config

Perfectly valid. Copying the other way might (or might not) result in invalid options in .gitconfig, which probably ought to be warned about. But the syntax is obviously identical.

Show 6 quoted lines

>> Calling it something else would imply that it deserves its own man
>> page, which would need to repeat all the options that are already
>> documented for ~/.gitconfig.
>
> No because most of those options don't and can't apply to a distributed
> option file.

But the ones that *do* apply all have the same meanings.

>> I'd say something that's syntactically identical, and in some cases
>> actually interchangeable, should have the same name.
>
> Indeed.  But this is not the case here.

Hmm, how to name the file is most a matter of opinion, but this last bit is just factual ;) They're syntactically identical. And in some cases, they're interchangeable. I don't see how one could argue otherwise.

Have fun,

Avery