On Mon, Mar 05, 2018 at 06:17:27PM -0800, Taylor Blau wrote: > The documentation for the `git-config(1)` builtin has not been recently > updated to include new types, such as `--bool-or-int`, and > `--expiry-date`. To ensure completeness when adding a new type > specifier, let's update the existing documentation to include the new > types. > > This commit also prepares for the new type specifier `--color`, so that > this section will not lag behind when yet more new specifiers are added. Good catch. Thanks for cleaning this up. > -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), or `--path`, which does some > -path expansion (see `--path` below). If no type specifier is passed, no > -checks or transformations are performed on the value. > +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? -Peff
