summaryrefslogtreecommitdiff
path: root/config.c
diff options
context:
space:
mode:
authorMartin Ågren <martin.agren@gmail.com>2017-08-07 20:20:49 +0200
committerJunio C Hamano <gitster@pobox.com>2017-08-07 13:29:22 -0700
commit8957661378b073b49875059d6426614facb0d7f0 (patch)
treed0ab9bbeb05fc9687b9823876bc1322fd2b35453 /config.c
parent4666741823239ed45ce9a63914dfd3c1601cf868 (diff)
downloadgit-8957661378b073b49875059d6426614facb0d7f0.tar.gz
treewide: deprecate git_config_maybe_bool, use git_parse_maybe_bool
The only difference between these is that the former takes an argument `name` which it ignores completely. Still, the callers are quite careful to provide reasonable values for it. Once in-flight topics have landed, we should be able to remove git_config_maybe_bool. In the meantime, document it as deprecated in the technical documentation. While at it, document git_parse_maybe_bool. Signed-off-by: Martin Ågren <martin.agren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'config.c')
-rw-r--r--config.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/config.c b/config.c
index 25d798f4cf..434a7daf19 100644
--- a/config.c
+++ b/config.c
@@ -1617,7 +1617,7 @@ int git_configset_get_maybe_bool(struct config_set *cs, const char *key, int *de
{
const char *value;
if (!git_configset_get_value(cs, key, &value)) {
- *dest = git_config_maybe_bool(key, value);
+ *dest = git_parse_maybe_bool(value);
if (*dest == -1)
return -1;
return 0;