Re: Implementing branch attributes in git config

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Sun, 7 May 2006, Linus Torvalds wrote:

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

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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]