sean <seanlkml@sympatico.ca> writes: > On Sun, 07 May 2006 18:27:32 -0700 > Junio C Hamano <junkio@cox.net> wrote: > > >> How about keeping the default syntax as it is (tokens are case >> insensitive and alnums only, dot separates tokens into >> sections), and when a token that violates that rule needs to be >> spelled out, require quoting, so: >> >> branch.foo BranCh.FoO branch.FOO > >> are the same (section "branch.foo"), > > Doesn't that mean you have to then prohibit creating mixed > case branches with "git branch" and "git checkout -b" ? Not at all. Whatever Porcelain that runs repo-config to record the branch name needs to spell that branch name with proper quoting, like: >> branch."js/fmt.patch" or "branch.js/fmt.patch" >> >> and the URL variable for that section is >> >> $ git repo-config '"branch.js/fmt.patch".url' > > How about transforming slashes into dots? so the above would > be: > > [branch.js.fmt.patch] I _do_ want to keep my slashes intact and also dots; mangling them is not very nice to me X-<. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Mon May 08 12:31:13 2006
This archive was generated by hypermail 2.1.8 : 2006-05-08 12:31:41 EST