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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Mar 20, 2010 at 10:09, Nguyen Thai Ngoc Duy <pclouds@xxxxxxxxx> wrote:
> On 3/20/10, Junio C Hamano <gitster@xxxxxxxxx> wrote:
>> Alex Riesen <raa.lkml@xxxxxxxxx> writes:
>>
>>  > The values passed this way will override whatever is defined
>>  > in the config files.
>>  >
>>  > Signed-off-by: Alex Riesen <raa.lkml@xxxxxxxxx>
>>  > ---
>>  >
>>  > 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]