summaryrefslogtreecommitdiff
path: root/t/t1300-config.sh
diff options
context:
space:
mode:
authorMatthew Rogers <mattr94@gmail.com>2020-02-10 00:30:58 (GMT)
committerJunio C Hamano <gitster@pobox.com>2020-02-10 18:49:12 (GMT)
commit9a83d088ee00dcdab171b2020ab334e369437a33 (patch)
tree8b21354f71400dc4fca02ff91bd76210b3c91b02 /t/t1300-config.sh
parente37efa40e122c4408c89c437e8a375df2147feac (diff)
downloadgit-9a83d088ee00dcdab171b2020ab334e369437a33.zip
git-9a83d088ee00dcdab171b2020ab334e369437a33.tar.gz
git-9a83d088ee00dcdab171b2020ab334e369437a33.tar.bz2
submodule-config: add subomdule config scope
Before the changes to teach git_config_source to remember scope information submodule-config.c never needed to consider the question of config scope. Even though zeroing out git_config_source is still correct and preserved the previous behavior of setting the scope to CONFIG_SCOPE_UNKNOWN, it's better to be explicit about such situations by explicitly setting the scope. As none of the current config_scope enumerations make sense we create CONFIG_SCOPE_SUBMODULE to describe the situation. Signed-off-by: Matthew Rogers <mattr94@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t1300-config.sh')
0 files changed, 0 insertions, 0 deletions