There is also a case insensitive alternative [section.subsection] syntax. In this syntax, subsection names follow the same restrictions as for section names.
If I define [section.SUBSECTION] (aka, not all lowercase), I cannot use: git config section.SUBSECTION.option, but rather only git config section.subsection.option. Furthermore, If I also define a [section "SUBSECTION"], the two sections are not merged. I believe this differs from the case insensitity that is used for sections: [section] and [SECTION] would be considered the same section. Is this the proper behaviour for the case insensititve alternative for subsections? -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/EeobUmDP5NsJ. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
