Re: Implementing branch attributes in git config

From: sean <seanlkml@sympatico.ca>
Date: May 8, 2006, 01:34 UTC
Message-ID: <BAYC1-PASMTP0334B471C6908E4E40BFD2AEA80@CEZ.ICE>
In-Reply-To: <7vfyjli9vf.fsf@assigned-by-dhcp.cox.net>

On Sun, 07 May 2006 18:27:32 -0700 Junio C Hamano <junkio@cox.net> wrote:

Show 6 quoted lines

> 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" ?

Show 9 quoted lines

> and if I have js/fmt.patch
> branch, I need to spell the configuration for that branch like
> so:
> 
> 	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]

      And could be accessed by either:

    $ git repo-config branch.js.fmt.patch
    $ git repo-config branch.js/fmt.patch

> (BTW, you could even have a variable with dots in it by quoting
> the variable name, like "branch.js/fmt.patch"."fetch.option"; I
> do not know if it is worth it).

Not worth it.  Branch names should be alnums and imho should be
case sensitive too.

> My repository is full of topic branches that are named xx/yyyy.
> It is very handy to be able to say "show-branch --topics master
> 'heads/??/*' next" which would not show my other branches like
> "test", "throwaway", "rework", "temp", etc.

Very nice.

Sean