On 1/10/06, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote: > > > > Can we teach the git:// fetch program to use CONNECT over HTTP > > > > proxies? rsync can do this, but git:// cannot, so firewalls that block > > > > 9418 mean we use rsync:// > > > > > > I think it is good and well with the proxy command support. Everybody can > > > write a little script. > > > > > > Otherwise, where would it end? If you include http_proxy functionality in > > > git, why not also https_proxy functionality? And if that, why not > > > > And, BTW, why not? It may as well stop here. > > Because it's not the purpose of git. It is the purpose of a tunnel. Let's > not make the mistake of Microsoft here: integrate everything until > everything breaks. Of course, I do not propose to put the code into connect.c! Let it be ip-tunnel.pl, or something like that (which btw is really awkward to handle under a well-known disabled OS). But, it is not exactly standard tunnel, is it? I mean, can you use it for something else? If not, is there really a point _not_ to put it in the git repository? As tunnel script or program, or as an instruction file on how to setup a firewall? - 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.htmlReceived on Wed Jan 11 04:33:59 2006
This archive was generated by hypermail 2.1.8 : 2006-01-11 04:34:06 EST