Now that I have moved the repository for ArmedBear to c-l.net, I'm
receiving request regarding HTTP(S) access. I know it's not there atm,
but.. what chances are there for it to become available?
Bye,
Erik.
I would like to point out that many FSFS Subversion repositories may
benefit from being stored on a filesystem with a small blocksize:
every revision consists of 2 files, these files contain differences
with respect to earlier versions. The effect is that if people do
small commits (which most lispers seem to do), most of both 4k blocks
gets waisted.
I'm pointing this out because drewc mentioned working at configuring a
new box for c-l.net.
Bye,
Erik.
So, has anybody else had this problem yet: It's been too long since I
logged into Trac for usocket and now I forgot the password I use to
edit the content.
The problem being that I can't find in Trac how to reset it :-(
Bye,
Erik.
I'd like to tweak the mailman settings a bit; does anyone know offhand
where the templates settings are located?
thanks,
--
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM
Hi Erik,
I need the following mailing list passwords reset:
cl-variates-announce
ait-devel
ait-announce
my apologies for the bother.
--
Gary Warren King, metabang.com
Cell: (413) 885 9127
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM
Hi
I have not been able to get to http://common-lisp.net for the whole
morning. I thought it was something on my wireless side, but I am
now connected to a wire and I can navigate fine.
--
Marco Antoniotti
Hi.
For all projects I have started on common-lisp.net, I have always set
up an auto-website-updater to sync the repository with the website in
<project>/public_html. Having just set up the py-configparser project,
I decided to take the default post-commit as a basis and extend it.
So, I'd like to request the default post-commit to be changed to what
is currently in /project/py-configparser/svn/hooks/post-commit.
What's changed? The lines starting with PROJECT=...
The script assumes the standard c-l.net setup where repositories
reside in the svn/ directory within the project root, next to the
public_html/ web-root. All it does is find out if the webroot is
versioned (it's not if svnversion prints "exported") and when it is,
it runs "svn update" on it. This means that projects will by default
have unversioned webroots, but as soon as they make them versioned
(checked out from the project repository), it'll be updated
automatically.
Thanks for your time and attention!
bye,
Erik.