On Monday 05 October 2009, Rolf Meeser wrote: > Hi David, > > > Right now I think there seems to be general agreement to > > switch to that GIT repository in the next couple of days. > > (So I encourage everyone to switch ASAP ...) > > I felt encouraged immediately,
Yay! > but now I'm stuck... Boo! > Has anyone solved the problem of git access from behind a > strict HTTP proxy? I thought that had been solved for some time now. As I look at the sourceforge service, I observe that it doesn't support http access though (except gitweb; not "git pull"). And since I don't have that unfortunate problem, I'm not up on the details. I do know there are various drawbacks to HTTP access, including slow speed. > Various recipes circulate the net, but none of them has > helped me so far. My only way out is through the HTTP > proxy. I assume that the proxy doesn't accept the git port, > and I have no possibility to change that. > > Can Sourceforge be configured for HTTP access, or is the > git protocol the only option? For SourceForge, I think it's just HTTP. Did you look around much? I'd hope that would be a FAQ, but ISTR that last year this time SF didn't offer GIT; so their service is evolving. Maybe if we asked, they'd help. :) One option would be to tunnel using SSH through the proxy, something like CorkScrew: http://returnbooleantrue.blogspot.com/2009/06/using-github-through-draconian-proxies.html which I found at http://github.com/guides/dealing-with-firewalls-and-proxies That also lists a Windows-oriented variant. Lacking that, we might want a git mirror at a site which does have easier HTTP access. We'll have to leave the important details here up to the folk who will be using the solutions though... - Dave _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
