Re: [PATCH] Allow passing of configuration parameters in the command line

From: Alex Riesen <raa.lkml@gmail.com>
Date: Mar 20, 2010, 09:17 UTC
Message-ID: <81b0412b1003200217m39c79418w54ac0735e8e6405a@mail.gmail.com>
In-Reply-To: <fcaeb9bf1003200209r6051f906kf2a0a1e96752845e@mail.gmail.com>

On Sat, Mar 20, 2010 at 10:09, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:

Show 21 quoted lines

> On 3/20/10, Junio C Hamano <gitster@pobox.com> wrote:
>> Alex Riesen <raa.lkml@gmail.com> writes:
>>
>>  > The values passed this way will override whatever is defined
>>  > in the config files.
>>  >
>>  > Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
>>  > ---
>>  >
>>  > Someone wanted to have this once. I accidentally remembered
>>  > that when I wanted to temporarily set some config parameter
>>  > (format.suffix?). From looking at code it seemed simple enough,
>>  > so I did it.
>>
>> How does this interact with core.worktree and the setup sequence in
>>  general?
>
> To me it looks like another config file to the config stack. No thing
> can go worse (except that if you have core.worktree in
> $GIT_DIR/config, now also specify -c core.worktree=foo, then
> core.worktree code would be called twice).

Yes, that's why I said the whole thing is not very friendly. To an experienced user it will be expected, though.