On Sun, 7 May 2006, sean wrote: > On Sun, 07 May 2006 19:29:50 -0700 > Junio C Hamano <junkio@xxxxxxx> wrote: > > > > Not at all. Whatever Porcelain that runs repo-config to record > > the branch name needs to spell that branch name with proper > > quoting, like: > > Okay. It just seems nuts to require quoting because you happen > to use an uppercase character. People are used to quoting > special characters like * and $, not uppercase letters. You could tell people always to use: [branch."name"] even if the branch name is all lowercase anyway. They could even use: [Branch."MyMixedCaseBranch"] Then when you refer to something case-sensitive with the possibility of funny characters, you put it in quotes, regardless of what it is. For that matter, we could retain the quotes when we parse the file, and reject [branch.master] for lacking the quotes, so that people who are only exposed to branch names all in lowercase letters don't get habits that will fail when they have a v2.6.16.x branch. I don't think that people are likely to use older versions of git on the same repository they've used newer versions on. (Clones of it, sure, but that doesn't matter here.) But we should, in any case, make the code ignore sections or lines with syntax errors, under the assumption that they're a later extension and possibly legal but not anything the code could be interested in getting from a parser that doesn't support them. -Daniel *This .sig left intentionally blank* - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html