| commit | 8957661378b073b49875059d6426614facb0d7f0 | |
| author | Martin Ågren <martin.agren@gmail.com> | |
| Mon, 7 Aug 2017 18:20:49 +0000 (7 20:20 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 7 Aug 2017 20:29:22 +0000 (7 13:29 -0700) | ||
| tree | d0ab9bbeb05fc9687b9823876bc1322fd2b35453 | treesnapshot (tar.gz zip) |
| parent | 4666741823239ed45ce9a63914dfd3c1601cf868 | commitdiff |
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>
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>