Thread (21 messages) flat view 21 messages, 6 authors, 2016-06-15

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

From: Jakub Narebski <hidden>
Date: 2016-06-15 22:51:29

René Scharfe [off-list ref] writes:
Am 16.06.2011 00:30, schrieb Jeff King:
quoted
On Tue, Jun 14, 2011 at 04:45:21PM -0400, Jeff King wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help