Lukas Fleischer <lfleisc...@lfos.de> writes:
> 1. There does not seem to be a way to pass configuration parameters to
> git-shell commands. Right now, the only way to work around this seems
> to write a wrapper script around git-shell that catches
> git-receive-pack commands and executes something like
>
> git -c receive.hideRefs=[...] receive-pack [...]
>
> instead of forwarding those commands to git-shell.
This part we have never discussed in the thread, I think. Why do
you need to override, instead of having these in the repository's
config files?
Is it because a repository may host multiple pseudo repositories in
the form of "namespaces" but they must share the same config file,
and you would want to customize per "namespace"?
For that we may want to enhance the [include] mechanism. Something
like
[include "namespace=foo"]
path = /path/to/foo/specific/config.txt
[include "namespace=bar"]
path = /path/to/bar/specific/config.txt
Cc'ing Peff as we have discussed this kind of conditional inclusion
in the past...
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
