@matheusbsbs / matheus-bagliano / commits / b7ee2266fe
Fork 0

config.txt: clarify sentences in the configuration and syntax sections

Signed-off-by: Stephen Boyd <bebarino@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Stephen Boyd committed Apr 23, 2009 at 02:38 UTC b7ee2266fe2d8593d4c2affdc3361836ce826230
1 file changed +6 -6
Documentation/config.txt
+6 -6
@@ -8,9 +8,9 @@ is used to store the information for that repository, and
8 fallback values for the `.git/config` file. The file `/etc/gitconfig`
9 can be used to store system-wide defaults.
10
11 -They can be used by both the git plumbing
12 -and the porcelains. The variables are divided into sections, where
13 -in the fully qualified variable name the variable itself is the last
11 +The configuration variables are used by both the git plumbing
12 +and the porcelains. The variables are divided into sections, wherein
13 +the fully qualified variable name of the variable itself is the last
14 dot-separated segment and the section name is everything before the last
15 dot. The variable names are case-insensitive and only alphanumeric
16 characters are allowed. Some variables may appear multiple times.
@@ -38,9 +38,9 @@ in the section header, like in the example below:
38
39 --------
40
41 -Subsection names can contain any character except newline (doublequote
42 -`"` and backslash have to be escaped as `\"` and `\\`,
43 -respectively) and are case sensitive. Section headers cannot span multiple
41 +Subsection names are case sensitive and can contain any characters except
42 +newline (doublequote `"` and backslash have to be escaped as `\"` and `\\`,
43 +respectively). Section headers cannot span multiple
44 lines. Variables may belong directly to a section or to a given subsection.
45 You can have `[section]` if you have `[section "subsection"]`, but you
46 don't need to.