git config 문자 규범

참조:https://git-scm.com/docs/git-config#_syntax
The syntax is fairly flexible and permissive; whitespaces are mostly ignored. The # and ; characters begin comments to the end of line, 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 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.
Sections can be further divided into subsections. To begin a subsection put its name in double quotes, separated by space from the section name, in the section header, like in the example below:

[section "subsection"]

Subsection names are case sensitive and can contain any characters except newline and the null byte. Doublequote "and backslash can be included by escaping them as "and\, respectively. Backslashes preceding other characters are dropped when reading; for example,\t is read as t and\0 is read as 0 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.
There is also a deprecated [section.subsection] syntax. With this syntax, the subsection name is converted to lower-case and is also compared case sensitively. These subsection names follow the same restrictions as section names.
All the other lines (and the remainder of the line after the section header) are recognized as setting variables, in the form name = value (or just name, which is a short-hand to say that the variable is the boolean “true”). The variable names are case-insensitive, allow only alphanumeric characters and -, and must start with an alphabetic character.
A line that defines a value can be continued to the next line by ending it with a ; the backquote and the end-of-line are stripped. Leading whitespaces after name =, the remainder of the line after the first comment character # or ;, and trailing whitespaces of the line are discarded unless they are enclosed in double quotes. Internal whitespaces within the value are retained verbatim.
Inside double quotes, double quote "and backslash\characters must be escaped: use "for "and\for .
The following escape sequences (beside "and\) are recognized: for newline character (NL),\t for horizontal tabulation (HT, TAB) and\b for backspace (BS). Other char escape sequences (including octal escape sequences) are invalid.