From: Dominik Fischer <d.f.fischer@web.de>
Date: Thu, 21 Apr 2016 16:30:04 GMT
Subject: Re: [PATCH/RFC/GSoC 0/2] add a add.patch config variable
Message-ID: <34fb607f-1c4c-528a-cb5d-eca95e0e7c68@web.de>
In-Reply-To: <alpine.DEB.2.20.1604211737170.2826@virtualbox>

Indeed this needs more explanations for everyone who did not read the 
posts before.

I strove to create an add.patch configuration option that did the same 
as always passing the parameter --patch to git-add. Junio C Hamano then 
made me aware that when set, this option would influence and possibly 
destroy other commands that internally use git-add. So I implemented the 
recursion counter, which is now the first of the two commits. With this, 
git-add is able to only consider the configuration option when run 
directly by the user, not affecting any commands building upon it.

I would be interested whether this is a suited method to restrict the 
effect of a configuration option to cases where a command is explicitly 
invoked by the user.

Regards.