Show 17 quoted lines
> Paul Collins <paul@briny.ondioline.org> writes:
>
>> But perhaps I do not really understand your objection.
>
> No, I think you are getting it right.
>
> I just wanted to avoid using the proxy script for some hosts,
> depending on where you are going. Obviously you can teach the
> proxy script to do passthru for some hosts like you did in your
> message. The only difference is where the configuration is
> specified. I wanted it to be in the git configuration file
> (i.e. using different proxy script or no script, depending on
> the host). Your example has that configuration wired in the
> single script that is always called regardless of the
> destination, and the script itself switches how it proxies,
> depending on where it is going, perhaps using its own
> configuration file or hardcoding.
I had some ideas along those lines, but I didn't like any of them.
* Extend the proxy-command "protocol" with a third argument, an
action. For example if 'query $host $port' returns successfully,
then git should run it with arguments 'connect $host $port',
otherwise use git_tcp_connect().
* Add a Proxy-Command field to the files in .git/remotes, e.g.:
URL: git://git.kernel.org/pub/scm/git/git.git/
Pull: master:origin
Proxy-command: my-git-proxy-command * If the git config syntax is extended to allow dots in section or
key names:
[proxy]
git.kernel.org = "ssh-to-bastion-proxy-command"
git.blargco.com = "blargco-proxy-command" or perhaps
[git.kernel.org]
proxycommand = "ssh-to-bastion-proxy-command"
[git.blargco.com]
proxycommand = "blargco-proxy-command"