Re: [PATCH] Allow default core.logallrefupdates to be overridden with template's config

From: Junio C Hamano <junkio@cox.net>
Date: Jan 24, 2007, 01:51 UTC
Message-ID: <7v4pqhkx93.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.63.0701240245440.22628@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 9 quoted lines

>> While on the topic of config files, we should fix the config
>> reader not to allow per-repository variables in ~/.gitconfig
>
> So we finally get this central place where all possible config variables 
> are listed, with options (a la struct cmd_struct) which tell more about 
> where they may be used?
>
> While I think this might make sense, I feel quite uneasy about such a 
> drastic change between -rc2 and -final.

I do not like the "config registry" in 1.5.0 but a simple blacklisting should work, shouldn't it?