Re: [PATCH] RFC: proxy-command support for git://

From: Linus Torvalds <torvalds@osdl.org>
Date: Nov 3, 2005, 19:22 UTC
Message-ID: <Pine.LNX.4.64.0511031117290.27915@g5.osdl.org>
In-Reply-To: <7v8xw5h898.fsf@assigned-by-dhcp.cox.net>

On Thu, 3 Nov 2005, Junio C Hamano wrote:

Show 14 quoted lines

> Paul Collins <paul@briny.ondioline.org> writes:
> 
> > I spend some of my time using a network that only allows outgoing TCP
> > connections to certain ports, and the git-daemon port is not one of them.
> > This patch below implements an analogue to ssh's ProxyCommand feature
> > for git, as a less messy alternative to ssh port forwarding.
> 
> Wonderful.
> 
> > Questions:
> >
> > * Can git already do this and I just failed to notice?
> 
> Maybe I just failed to notice this too, but I do not think so.

Actually, you could. TWO ways, in fact, afaik.

Just use the "ssh://host/pathname" format (or just "host:pathname") and the GIT_SSH environment variable.

You could also override the local command-name with

	git-send-pack --exec=my-local-send-program /machine/repo/path

where the "my-local-send-program" will parse /machine/repo/path thing. At least that works with git-send-pack, but it's possible it doesn't work with some other logic (ie "git push" might decide that it's unhappy that /machine/repo/path doesn't exist locally because it thinks it's a local path).

		Linus