On 2008-12-13, Nix <nix@xxxxxxxxxxxxx> wrote: > telnet. I do not jest, this is our sysadmins' stated reasons for not > opening the git port and for tweaking their (mandatory) HTTP proxy to > block HTTP traffic from git. Wow -- my sympathies! But on occasion, when real or imaginary issues prevented me from making a live connection, I have used "git bundle" to do the job. Not as satisfactory as a real connection, but when you have a proper, non-fast-forwarding, repo as the "mother ship", git bundle with some custom procmail scripts on both sides can work OK enough. To do that with a public repo you'd have to mirror that on a home machine and let your restricted environment work against that. > Do not underestimate the stupidity and hideboundedness of undertrained > system administrators, for it is vast. These same administrators also underestimate (i) the number of well connected home machines and (ii) the idea that on his own machine, everyone is root. Most of these blocks are "default allow", and your home IP is not on that list and they don't have the smarts to figure out that you're getting around their blocks :-) Add dynamic IP and a dyndns hostname (and dyndns has a hundred or so 2nd level domains to choose your 3rd level hostname from!) and clueless admins don't stand a chance. [sorry this is so badly off-topic...] -- 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
