[iterate-devel] devel access?

Marco Baringer mb at bese.it
Wed Feb 23 11:01:53 UTC 2005


"Hoehle, Joerg-Cyril" <Joerg-Cyril.Hoehle at t-systems.com> writes:

> I'm not at all against it. My experience with CLISP is that I prefer
> to get my stuff in *and then* let people possibly change it, instead
> of having somebody play the filter first in the line, breaking my
> stuff and causing me more work.

ok. you'll need a cl.net account then, could you send
admin at common-lisp.net your gpg key?

> However, I've some technical hurdles. I'm coming from within a
> corporate firewall, permitting FTP, HTTP and HTTPS and I think
> that's all. I manage to reach the CVS devel access to sourceforge
> (for CLISP) because they provide cvs-ssh (i.e. the connection looks
> to firewalls and proxies like a typical SSL one). I can't use
> anon-cvs AFAIK.

if you can use ssh to connect to cl.net then we can just keep the
current setup. if https is your only option then we'd need to get
webdav+https installed on cl.net (which wouldn't be a bad thing
anywoy).

as far as the version control system used goes i'd prefer arch as it's
already installed and iterate's already using it. however you are
doing all the work lately, not I, and so i'll see about getting
whatever you like best. [both arch and svn will run under ssh and/or
https+webdav]

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen



More information about the iterate-devel mailing list