Jeff King <peff@xxxxxxxx> writes:
>> +The type specifier can be either `--int` or `--bool`, to make 'git config'
>> +ensure that the variable(s) are of the given type and convert the value to the
>> +canonical form (simple decimal number for int, a "true" or "false" string for
>> +bool, either of for --bool-or-int), or `--path`, which does some path expansion
>> +(see `--path` below), or `--expiry-date` (see `--expiry-date` below). If no
>> +type specifier is passed, no checks or transformations are performed on the
>> +value.
>
> Perhaps it's time to switch to a list format for these?
A very sensible suggestion. The original was already bad enough but
with complete set, it does become quite hard to read. Perhaps along
the lines of...
A type specifier option can be used to force interpretation of
values and conversion to canonical form. Currently supported
type specifiers are:
`--int`::
The value is taken as an integer.
`--bool`::
The value is taken as a yes/no value, and are shown as
"true" or "false".
...
