Re: [PATCH] Teach 'git apply' to look at $GIT_DIR/config

From: Junio C Hamano <junkio@cox.net>
Date: Feb 18, 2007, 00:28 UTC
Message-ID: <7vbqjsqpgs.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.63.0702180107250.22628@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 11 quoted lines

>> > If I read this correctly, running 'git apply' inside a git repository
>> > will parse $GIT_DIR/config and $HOME/.gitconfig. However, outside of a
>> > repository it will parse neither. It would make more sense to me to
>> > still parse $HOME/.gitconfig to pick up the user's global options.
>> 
>> I thought about that, but decided against it.  If you are truly
>> operating outside a git managed repository, it does not feel
>> right to apply configuration user has for git.
>
> That is a good point. But in the same vein, why not have a flag to 
> git-apply, and let it ignore the configuration altogether?

Do you mean --whitespace=strip option from the command line?

But I think Jeff is right. It would make sense to let apply and perhaps 'diff', if we can somehow merge 'diff2' into it, still read from $HOME/.gitconfig if available.