summaryrefslogtreecommitdiff
path: root/t/t4136-apply-check.sh
diff options
context:
space:
mode:
authorLibravatar Martin Ågren <martin.agren@gmail.com>2017-08-07 20:20:47 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2017-08-07 13:27:23 -0700
commit9be04d64c9b45a37cba161ba2eff2e784f87f91a (patch)
treece6be2b7ca3fbd3035e3cb7c1b05e28dbf4c93c2 /t/t4136-apply-check.sh
parentt5334: document that git push --signed=1 does not work (diff)
downloadtgif-9be04d64c9b45a37cba161ba2eff2e784f87f91a.tar.xz
config: introduce git_parse_maybe_bool_text
Commit 9a549d43 ("config.c: rename git_config_maybe_bool_text and export it as git_parse_maybe_bool", 2015-08-19) intended git_parse_maybe_bool to be a replacement for git_config_maybe_bool, which could then be retired. That is not obvious from the commit message, but that is what the background on the mailing list suggests [1]. However, git_{config,parse}_maybe_bool do not handle all input the same. Before the rename, that was by design and there is a caller in config.c which requires git_parse_maybe_bool to behave exactly as it does. Prepare for the next patch by renaming git_parse_maybe_bool to ..._text and reimplementing the first one as a simple call to the second one. Let the existing users in config.c use ..._text, since it does what they need. [1] https://public-inbox.org/git/xmqq7fotd71o.fsf@gitster.dls.corp.google.com/ Signed-off-by: Martin Ågren <martin.agren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4136-apply-check.sh')
0 files changed, 0 insertions, 0 deletions