Re: [PATCH 2/2] repo-config: learn the flag "--no-local"

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jun 8, 2006, 20:24 UTC
Message-ID: <Pine.LNX.4.63.0606082222470.28323@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <BAYC1-PASMTP04DDBAA584B31A4B0F31DCAE8B0@CEZ.ICE>

Hi,

On Thu, 8 Jun 2006, Sean wrote:

Show 17 quoted lines

> On Thu, 08 Jun 2006 09:25:53 -0700
> Junio C Hamano <junkio@cox.net> wrote:
> 
> 
> > The wording "--no-local" means you are looking at things
> > relative to a particular repository.  I.e. some configuration
> > variables come from repository-local file, and others from
> > somewhere else.  But I do not think that somewhere else is
> > "global".  We are reading from $HOME, which is different
> > depending on who is interacting with that same repository.  So I
> > would probably call the other one "--user" or something if I
> > were force to pick name.
> 
> --user or --home makes a lot of sense.  Alternatively you could
> just be explicit: --config=~ or --config=/etc/gitconfig where
> /.gitconfig is automatically appended to the path if it ends in
> a directory name.

I think --user makes more sense than --home, since it does not matter _where_ it is stored, but _when_ it is retreived.

In the same vein, I do not think it is user friendly to expect the user to remember if it was .gitconfig, .git or .gitrc.

Ciao, Dscho