Re: 0.99.9 on Saturday next week.

From: Linus Torvalds <torvalds@osdl.org>
Date: Oct 25, 2005, 17:41 UTC
Message-ID: <Pine.LNX.4.64.0510251033310.10477@g5.osdl.org>
In-Reply-To: <7virvlh6m5.fsf@assigned-by-dhcp.cox.net>

On Tue, 25 Oct 2005, Junio C Hamano wrote:

Show 9 quoted lines

>
> Catalin Marinas <catalin.marinas@gmail.com> writes:
> 
> >>  - Configuration files (Linus).
> >
> > Since the configuration files use the .ini like syntax, is it OK for
> > StGIT to use the same file, with an "[stgit]" section?
> 
> I think that is a reasonable thing to do.

Absolutely. The whole thing was _designed_ to be used that way. Any C user should be able to just link against config.o without even bothering with the rest of git (the only git-specific thing there should be some naming), and any script user can either

 - parse the simple config language by hand (not really a good idea, but 
   it _is_ pretty simple)
 - just run "git-var -l" and parse the output.

ie if you want to track "[stgit]" config options, just do

	git-var -l | sed '/^stgit\./ s/^stgit.//p'

and it will pick up everything starting with "stgit." and remove that part.

What remains should be a simple list or "variable=value" pairs.

Oh - and the convention is that

 (a) we've already done any quote expansion (although I may have to make 
     git-var quote "\n" - I didn't care enough to do so)
 (b) a boolean variable without a "=" means that it was set to "true" 
     (which is different from an _empty_ one, which has a "=" but just 
     doesn't have any value)

The (b) thing is just a special case, so that you can write

	[stgit]
		debug

and it will be the same as

	[stgit]
		debug = true

which just seems to be the sane thing to do.

		Linus