From: Carl Baldwin <cnb@fc.hp.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>,
Paul Collins <paul@briny.ondioline.org>,
git@vger.kernel.org
Subject: Re: [PATCH] RFC: proxy-command support for git://
Date: Thu, 3 Nov 2005 13:41:37 -0700 [thread overview]
Message-ID: <20051103204137.GA1343@hpsvcnb.fc.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0511031117290.27915@g5.osdl.org>
Another way to do this would be using the ~/.ssh/config file. It would
look something like this:
Host host
ProxyCommand ...
Or, more generically...
Host *.*
ProxyCommand ...
Host *.* assumes that if the machine name has a '.' in it then you are
trying to get outside the firewall. This might not be a good assumption
but it works well where I am.
Then use host:pathname or ssh://host/pathname or whatever.
The advantage of using this is that it works for anything that uses ssh
to get outside the firewall. Not just git. So, setup is minimal.
Carl
On Thu, Nov 03, 2005 at 11:22:35AM -0800, Linus Torvalds wrote:
>
>
> On Thu, 3 Nov 2005, Junio C Hamano wrote:
>
> > 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
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Carl Baldwin Systems VLSI Laboratory
Hewlett Packard Company
MS 88 work: 970 898-1523
3404 E. Harmony Rd. work: Carl.N.Baldwin@hp.com
Fort Collins, CO 80525 home: Carl@ecBaldwin.net
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
next prev parent reply other threads:[~2005-11-03 20:42 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
2005-11-03 19:22 ` Linus Torvalds
2005-11-03 20:41 ` Carl Baldwin [this message]
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=20051103204137.GA1343@hpsvcnb.fc.hp.com \
--to=cnb@fc.hp.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=paul@briny.ondioline.org \
--cc=torvalds@osdl.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).