Re: [PATCH] git config: clarify bool types

> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> The value is what it is, the --bool and --bool-or-int options don't
>> specify the value type, just how it is interpreted. For example: a value
>> of '1' can be interpreted as 'true'.
>>
>> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
>> ---
>>
>> This applies on top of the 'next' branch.
>>
>>  builtin-config.c |    4 ++--
>>  1 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/builtin-config.c b/builtin-config.c
>> index 1a3baa1..c3a0176 100644
>> --- a/builtin-config.c
>> +++ b/builtin-config.c
>> @@ -66,9 +66,9 @@ static struct option builtin_config_options[] = {
>>       OPT_STRING(0, "get-color", &get_color_slot, "slot", "find the color configured: [default]"),
>>       OPT_STRING(0, "get-colorbool", &get_colorbool_slot, "slot", "find the color setting: [stdout-is-tty]"),
>>       OPT_GROUP("Type"),
>> -     OPT_BIT(0, "bool", &types, "value is \"true\" or \"false\"", TYPE_BOOL),
>> +     OPT_BIT(0, "bool", &types, "value is intepreted as bool (\"true\" or \"false\")", TYPE_BOOL),
>
> I'd rater see it say something like:
>
>        Output the value as boolean (true or false)
>
> so that it is consistent with others you can see in the context.
> E.g. get-color explains it to order the command to "find the color".
>
> "Interpret" is fine too.  The point is not about the choice of verb but
> use of imperative mood.