Re: Implementing branch attributes in git config

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: May 8, 2006, 01:05 UTC
Message-ID: <Pine.LNX.4.63.0605080303410.13588@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <Pine.LNX.4.64.0605071718440.3718@g5.osdl.org>

Hi,

On Sun, 7 May 2006, Linus Torvalds wrote:

Show 27 quoted lines

> [...]
> 
> and if your branch names are purely alphabetical and lower-case, you can 
> now write
> 
> 	[branch.origin]
> 		remote = true
> 		url = git://git.kernel.org/...
> 		fetch = master
> 
> 	[branch.master]
> 		pull = origin
> 
> and it will be parsed _exactly_ the same as
> 
> 	["origin"]
> 		remote = true
> 		url = git://git.kernel.org/...
> 		fetch = master
> 
> 	["master"]
> 		pull = origin
> 
> while the [branch.origin] syntax allows old versions of git to happily 
> ignore it. So that would be a kind of cheesy work-around: the new 
> double-quoted format is only _required_ for any branch-names that have 
> special characters in it.

Eek.

The ["blablabla"] syntax fails the is-it-obvious-what-this-does test. What *is* wrong with the " for " syntax? IIRC it was even proposed by you, and it happens to be backward compatible.

Ciao, Dscho