From: Junio C Hamano <junkio@cox.net>
To: Paul Collins <paul@briny.ondioline.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] RFC: proxy-command support for git://
Date: Thu, 03 Nov 2005 10:54:43 -0800 [thread overview]
Message-ID: <7v8xw5h898.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 87fyqdbuab.fsf@briny.internal.ondioline.org
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.
> * Where should git_use_proxy() look? Some git configuration file?
> An environment variable? Both? Somewhere else?
My preference is put something in .git/config to describe which
proxy command (maybe the same one with different argument) to
use depending on where you are going. When you have internal
hosts and external hosts you would want this to apply only to
external hosts. Maybe you have two or more gateways and
depending on which external host you are going you may want to
use different proxied connection. On top of the config file,
making it overridable from an environment variable would be
sensible.
next prev parent reply other threads:[~2005-11-03 18:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 15:55 [PATCH] RFC: proxy-command support for git:// Paul Collins
2005-11-03 18:54 ` Junio C Hamano [this message]
2005-11-03 19:22 ` Linus Torvalds
2005-11-03 20:41 ` Carl Baldwin
2005-11-03 21:31 ` Junio C Hamano
2005-11-04 14:57 ` [PATCH] v2: " Paul Collins
2005-11-04 16:50 ` Junio C Hamano
2005-11-04 18:57 ` Junio C Hamano
2005-11-04 21:06 ` Paul Collins
2005-11-04 21:42 ` Junio C Hamano
2005-11-04 22:04 ` Paul Collins
2005-11-04 22:15 ` Linus Torvalds
2005-11-19 12:13 ` [PATCH] git-proxy updates Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v8xw5h898.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=paul@briny.ondioline.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).