Re: Implementing branch attributes in git config

From: Linus Torvalds <torvalds@osdl.org>
Date: May 9, 2006, 04:11 UTC
Message-ID: <Pine.LNX.4.64.0605082100460.3718@g5.osdl.org>
In-Reply-To: <BAYC1-PASMTP05953E2B948CB07A171FD8AEA90@CEZ.ICE>

On Mon, 8 May 2006, sean wrote:

Show 7 quoted lines

>
> [core]
>  ...
> [branch.core]
>  ...
> [remote.core]
>  ...

Ok. In that case, I would suggest a much more readable format:

	[core]
		...

	[branch "core"]
		...

	[remote "core"]
		...

and yes, enforce the <space>+<quoted name> format. We'd turn it internally into some random internal string format (probably replacing the space with a dot, and removing the quotes, so it would become "remote.core.<key>").

> But it's not just the config file, it's also how it ends up being used
> on the command line..

Actually, the command line migth as well allow any strange thing, and _add_ the quotes internally. So you could do something that does

	git repo-config set Remote.Core.Pull master

and we could just let that generate

	[remote "Core"]
		pull = master

or whatever.

I care about the _file_ being human-editable, but that means that I think it's perfectly fine to have some smarts in the tools that help us do so, and let them recognize the magic "remote" and "branch" prefixes.

		Linus