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

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 19, 2010, 19:36 UTC
Message-ID: <7vmxy4kss9.fsf@alter.siamese.dyndns.org>
In-Reply-To: <81b0412b1003190742v6e5577c9wb121d5e3cbc9fccd@mail.gmail.com>

Alex Riesen <raa.lkml@gmail.com> writes:

Show 10 quoted lines

> 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?

By "setup sequence", I mean something I tried to extract from Nguyen here:

 http://thread.gmane.org/gmane.comp.version-control.git/141962/focus=142001
 
During the process of finding the repository (.git/ or project.git/), we
would open its config to check the repository format version, that that
would be the earliest point we might decide where the work tree is (or if
we have work tree at all).  Where should this new mechanism hook into the
sequence to give users an expected behaviour (what's expected in the first
place)?