From: Junio C Hamano <junkio@cox.net>
To: Paul Collins <paul@briny.ondioline.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] v2: proxy-command support for git://
Date: Fri, 04 Nov 2005 13:42:28 -0800 [thread overview]
Message-ID: <7v3bmct7i3.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <87ll049l8a.fsf@briny.internal.ondioline.org> (Paul Collins's message of "Fri, 04 Nov 2005 21:06:13 +0000")
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.
next prev parent reply other threads:[~2005-11-04 21: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
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 [this message]
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=7v3bmct7i3.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).