Re: [RFC/PATCH 0/7] user-configurable git-archive output formats

From: Jakub Narebski <jnareb@gmail.com>
To: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Cc: Jeff King <peff@github.com>, Junio C Hamano <gitster@pobox.com>,
	"J.H." <warthog19@eaglescrag.net>,
	git@vger.kernel.org, git-dev@github.com
Subject: Re: [RFC/PATCH 0/7] user-configurable git-archive output formats
Date: Sat, 18 Jun 2011 08:28:48 -0700 (PDT)	[thread overview]
Message-ID: <m3wrgjtb1c.fsf@localhost.localdomain> (raw)
In-Reply-To: <4DFCBB92.5040308@lsrfire.ath.cx>

René Scharfe <rene.scharfe@lsrfire.ath.cx> writes:
> Am 16.06.2011 00:30, schrieb Jeff King:
>> On Tue, Jun 14, 2011 at 04:45:21PM -0400, Jeff King wrote:
>> 
>>> The gzip path is not configurable at all. Probably it should read the
>>> path and arguments from the config file. In fact, we could even allow
>>> arbitrary config like:
>>>
>>>   [tarfilter "tgz"]
>>>     command = gzip -c
>>>     extension = tgz
>>>     extension = tar.gz
> 
> Configuration options whose values are appended instead of overwritten
> by duplicate definitions are a new concept for git, I think.  Perhaps
> it's not a big thing, but I think it's better avoided.

Actually they are not a new concept, but they are quite rare.  `git config`
has even special options to deal with them ('--replace-all', '--add', 
'--get-all', '--unset-all'.

For example "core.gitProxy" can be set multiple times, and of course
"remote.<remotename>.fetch", 'pull' and 'url'.

-- 
Jakub Narebski
Poland
ShadeHawk on #git