summaryrefslogtreecommitdiff
path: root/t/t5531-deep-submodule-push.sh
diff options
context:
space:
mode:
authorStefan Beller <sbeller@google.com>2017-06-01 00:30:48 (GMT)
committerJunio C Hamano <gitster@pobox.com>2017-06-01 01:36:36 (GMT)
commit9071c078af637573a3068c6920dd4ceff6a5a69f (patch)
tree71590a61a533ec630a6af98f411725d5cfdb1116 /t/t5531-deep-submodule-push.sh
parent046b48239eca34425909330e59da57f5fd421bdc (diff)
downloadgit-9071c078af637573a3068c6920dd4ceff6a5a69f.zip
git-9071c078af637573a3068c6920dd4ceff6a5a69f.tar.gz
git-9071c078af637573a3068c6920dd4ceff6a5a69f.tar.bz2
builtin/grep.c: respect 'submodule.recurse' option
In builtin/grep.c we parse the config before evaluating the command line options. This makes the task of teaching grep to respect the new config option 'submodule.recurse' very easy by just parsing that option. As an alternative I had implemented a similar structure to treat submodules as the fetch/push command have, including * aligning the meaning of the 'recurse_submodules' to possible submodule values RECURSE_SUBMODULES_* as defined in submodule.h. * having a callback to parse the value and * reacting to the RECURSE_SUBMODULES_DEFAULT state that was the initial state. However all this is not needed for a true boolean value, so let's keep it simple. However this adds another place where "submodule.recurse" is parsed. Signed-off-by: Stefan Beller <sbeller@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5531-deep-submodule-push.sh')
0 files changed, 0 insertions, 0 deletions