From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Sat, 14 Feb 2009 19:24:19 GMT
Subject: Re: [PATCH] config: Use parseopt.
Message-ID: <alpine.DEB.1.00.0902142022340.10279@pacific.mpi-cbg.de>
In-Reply-To: <94a0d4530902141114s7352841cmf5c4259211a793e3@mail.gmail.com>

Hi,

On Sat, 14 Feb 2009, Felipe Contreras wrote:

> On Sat, Feb 14, 2009 at 9:11 PM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
> > Hi,
> >
> > On Sat, 14 Feb 2009, Felipe Contreras wrote:
> >
> >> 1) --list when no config file is given uses all the config files,
> >> wouldn't it make sense to have a --repo option?
> >
> > The idea of --list is not "cat .git/config".  The idea is to help users or
> > scripts to list the current settings (_including_ the global settings).
> >
> > You can force showing the repo-specific config with "git --file
> > .git/config", though.
> 
> When you are on the root directory of the repo, and you don't have
> GIT_DIR, or --git-dir.

When I wrote my response, I briefly considered if I had to be verbose, and 
decided against it.

But this is what I should have written:

	git --file $(git rev-parse --git-dir)/config --list

Ciao,
Dscho