Re: $GIT_CONFIG should either apply to all commands, or none at all

Jonathan Nieder writes: > Yep. One possibility would be to do something like the following (A): > > 1) advertise in the git-config(1) manpage that the GIT_CONFIG > environment variable only affects the behavior of the 'git config' > command > > 2) introduce an environment variable GIT_

Re: $GIT_CONFIG should either apply to all commands, or none at all

On Wed, Oct 01, 2014 at 06:15:46PM -0700, Jonathan Nieder wrote: > 3) Warn when 'git config' is called with GIT_CONFIG set, explaining > that support will eventually be removed and that callers should > pass --file= instead. > > 4) Once we're confident there are no scripts in the wild r

Re: $GIT_CONFIG should either apply to all commands, or none at all

Hi, Frédéric Brière wrote[1]: > This kind of stuff caused me a lot of hair-pulling: > > $ git config core.abbrev > 32 > git log --pretty=oneline --abbrev-commit > 89be foo > > Here's the source of the discrepancy: > > $ grep abbrev $GIT_CONFIG .git/config > git.conf: abbrev=32 > .