Re: Implementing branch attributes in git config

From: Junio C Hamano <junkio@cox.net>
Date: May 8, 2006, 02:29 UTC
Message-ID: <7vbqu9i6zl.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <BAYC1-PASMTP0334B471C6908E4E40BFD2AEA80@CEZ.ICE>

sean <seanlkml@sympatico.ca> writes:

Show 15 quoted lines

> 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:

Show 10 quoted lines

>> 	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-<.