Re: Get rid of .git/branches/ and .git/remotes/?

From: Josef Weidendorfer <josef.weidendorfer@gmx.de>
Date: Nov 22, 2005, 23:05 UTC
Message-ID: <200511230005.12957.Josef.Weidendorfer@gmx.de>
In-Reply-To: <Pine.LNX.4.63.0511221854120.27872@wbgn013.biozentrum.uni-wuerzburg.de>

On Tuesday 22 November 2005 18:56, Johannes Schindelin wrote:

> On Tue, 22 Nov 2005, Josef Weidendorfer wrote:
> >   [remote:origin]
> >     url = master.kernel.org:/pub/scm/git/git.git
> >     pull = master:origin

Show 6 quoted lines

> I don't know if you missed it, but hierarchical config keys were 
> introduced by b17e659dd4007cb1d3eb5ac32b524c0c5ab59601:
> 
> [remote.origin]
> 	url = master.kernel.org:/pub/scm/git/git.git
> 	pull = master:origin

I know. My suggestion complements hierarchical keys:

 [myporcelain.headproperties: my/head.name]
    merge.candidates = my/other.head
    merge.default = your/master

would be the same as

 [myporcelain.headproperties]
    merge.candidates = my/other.head for my/head.name
    merge.default = your/master for my/head.name

It is about specifying the same " for "-part for multiple keys. The idea is to use everything after a ":\s*" in a section name to use as prefix for any " for "-part of keys values given in this section.

Josef