Re: What's in git.git

From: Petr Baudis <pasky@suse.cz>
Date: Jun 18, 2006, 13:08 UTC
Message-ID: <20060618130837.GN2609@pasky.or.cz>
In-Reply-To: <Pine.LNX.4.63.0606181417090.26803@wbgn013.biozentrum.uni-wuerzburg.de>

Dear diary, on Sun, Jun 18, 2006 at 02:26:14PM CEST, I got a letter where Johannes Schindelin <Johannes.Schindelin@gmx.de> said that...

> There is one thing I don't like about Pasky's approach: You can change the 
> config file name to whatever you like, even if no program will read it. 
> That is why I decided to have a flag instead of an option: to prevent 
> pilot-errors.

I'm lost here, admittelly not getting your argument. :-(

Show 5 quoted lines

> I cobbled together a patch, which turned out to be rather messy, 
> introducing "--config-file <file>" to git-repo-config. If people are 
> interested, I'll clean it up and post it. But then, if you already know 
> you want to use another config file, you are probably better of just 
> exporting GIT_CONFIG_FILE and be done with it.

$GIT_CONFIG_FILE feels nicer since any other git tool can use it as well, it's not git-repo-config-specific. But the current intent indeed is to simply override the location for git-repo-config, thus for the current purposes if we will have --config-file instead of GIT_CONFIG_FILE, I will not weep; whatever does the job.

> Note that this issue is orthogonal to the need for a user-specific config 
> file. I still think that this one should go in.

I agree as well.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
A person is just about as big as the things that make them angry.