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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
