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. Signed-off-by: Taylor Blau <me@xxxxxxxxxxxx> --- Documentation/git-config.txt | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/Documentation/git-config.txt b/Documentation/git-config.txt index 390b49831..28d84ded9 100644 --- a/Documentation/git-config.txt +++ b/Documentation/git-config.txt @@ -38,12 +38,13 @@ existing values that match the regexp are updated or unset. If you want to handle the lines that do *not* match the regex, just prepend a single exclamation mark in front (see also <<EXAMPLES>>). -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. When reading, the values are read from the system, global and repository local configuration files by default, and options -- 2.15.1.354.g95ec6b1b3
