[iterate-devel] iterate repository
Hi, Andreas Fuchs wrote:
And it is done. Attila, you now have write permissions. When Joerg requests a cl.net account, I'll get him added, too.
I welcome Attila with write permissions. Indeed, the web site is bit rot and would benefit from benevolents. AFAIK, I don't "need" an account, because I cannot use it. I have no SSH permissions to the outside world. Last time I talked with Erik Enge (at most a month ago), there was no solution (yet) to this problem. However, I can use HTTP (to port 80 only, and maybe a few others) and HTTPS to the standard SSL port (443). Thus if there's a way to update a repository via these means, I'm in favour of using that. o darcs has afaik means to automatically integrate signed patches via e-mail. If Erik can set this up, it could be used. I've no experience with that, though. o maybe Arch has means to work only with HTTP and HTTPS, but so far, I found no indication that I can use Arch given my FW restrictions. Maybe I'm mistaken? o I have developer access to sourceforge. But that works only because they have a host (cvs-ssh.sourceforge.net) which maps the SSH port to the HTTPS one, so CVS gets through, as the FW believes it's doing HTTPS. Sourceforge is the only one I know which does that port mapping. Regards, Jorg Hohle.
On 2006-03-21, Joerg-Cyril Hoehle <Joerg-Cyril.Hoehle@t-systems.com> wrote:
Andreas Fuchs wrote:
And it is done. Attila, you now have write permissions. When Joerg requests a cl.net account, I'll get him added, too.
I welcome Attila with write permissions. Indeed, the web site is bit rot and would benefit from benevolents. AFAIK, I don't "need" an account, because I cannot use it. I have no SSH permissions to the outside world. Last time I talked with Erik Enge (at most a month ago), there was no solution (yet) to this problem.
However, I can use HTTP (to port 80 only, and maybe a few others) and HTTPS to the standard SSL port (443). Thus if there's a way to update a repository via these means, I'm in favour of using that.
Hah! Erik Enge just set up a port forwarding service on shell.common-lisp.net that has ssh listening on (among others) port 443. To get an account, you need to send him your full name, GPG key and e-mail address. Also, make sure to test if it really works for you, as per the instructions on <URL:http://common-lisp.net/faq.shtml>.
o I have developer access to sourceforge. But that works only because they have a host (cvs-ssh.sourceforge.net) which maps the SSH port to the HTTPS one, so CVS gets through, as the FW believes it's doing HTTPS. Sourceforge is the only one I know which does that port mapping.
Not anymore (-: Cheers, -- Andreas Fuchs, (http://|im:asf@|mailto:asf@)boinkor.net, antifuchs
participants (2)
-
Andreas Fuchs -
Hoehle, Joerg-Cyril