On Wed, 27 Feb 2008, Johannes Schindelin wrote: > On Wed, 27 Feb 2008, Ken Fuchs wrote: > > [Ken did not say who said this:] Sorry, Mike Hommey wrote the following on 27 Feb 2008: > > > git-clone is not a builtin yet. When it is (and a patch > > > has come for that), it will correctly use proxys. > > > > Is there a work-around for cloning a git repository via a proxy? > Yes. > > Just export "http_proxy". AFAICT this works... See > > http://repo.or.cz/w/msysgit.git?a=commitdiff;h=257a62710c0253d940a59b6fb 2f371afa84dcf56 > for a working example. Unfortunately, this will not work because "git clone" is implemented by git-clone.sh and has no support for dealing with proxies at all. Note that the example uses "git fetch" and not "get clone". So it seems that git's http protocol via a proxy isn't completely supported. For example, "git fetch" works with a proxy, since it is implemented via a builtin (executable) which includes proxy support. At least that is my understanding of Mike's comments above. The only work-around for "git clone" that I'm aware of is a "proxy agent" that intercepts and modifies all Internet bound requests and responses so they go (transparently) through the proxy server rather than directly to the Internet. Thus, none of the clients being used need to be proxy aware, including "git clone" (or any git function for that matter). However, I was looking for a different work-around for using "git clone" via http protocol and proxy (NTLM auth.), but there do not appear to be any. Thanks, Ken Fuchs -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
