[PATCH v2 1/7] Documentation/config.txt: avoid unnecessary negation
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 4, 2015, 21:33 UTC
- Message-ID
- <1425504803-16039-2-git-send-email-gitster@pobox.com>
- In-Reply-To
- <1425504803-16039-1-git-send-email-gitster@pobox.com>
Section names and variable names are both case-insensitive, but one is described as "not case sensitive". Use "case-insensitive" for both.
Instead of saying "... have to be escaped" without telling what that escaping achieves, state it in a more positive way, i.e. "... can be included by escaping".
Signed-off-by: Junio C Hamano <gitster@pobox.com> --- Documentation/config.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt index 097fdd4..dbe7035 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -25,7 +25,7 @@ blank lines are ignored. The file consists of sections and variables. A section begins with the name of the section in square brackets and continues until the next -section begins. Section names are not case sensitive. Only alphanumeric +section begins. Section names are case-insensitive. Only alphanumeric characters, `-` and `.` are allowed in section names. Each variable must belong to some section, which means that there must be a section header before the first setting of a variable. @@ -40,8 +40,8 @@ in the section header, like in the example below: -------- Subsection names are case sensitive and can contain any characters except -newline (doublequote `"` and backslash have to be escaped as `\"` and `\\`, -respectively). Section headers cannot span multiple +newline (doublequote `"` and backslash can be included by escaping them +as `\"` and `\\`, respectively). Section headers cannot span multiple lines. Variables may belong directly to a section or to a given subsection. You can have `[section]` if you have `[section "subsection"]`, but you don't need to.
-- 2.3.1-316-g7c93423