clo-devel

clo-devel@common-lisp.net

2 participants
609 discussions

[clo-devel] Two new projects
by Gary King 03 May '06

03 May '06

I am in the process of processing two new projects: cl-markdown: a Common Lisp port of John Gruber's markdown language with cool extensions to follow trivial-shell: a bare bones portable Common Lisp library to talk to the OS Both use the MIT license. thanks, -- Gary Warren King metabang.com http://www.metabang.com/ (413) 210 7511 gwking on #lisp (occasionally)

1 0

[clo-devel] /project/cl-irc/svn permissions
by Erik Huelsmann 09 Apr '06

09 Apr '06

Hi! I'm trying to switch cl-irc over to svn. I had an old import sitting in svn/, so I created another one and re-imported there, removed svn/ and renamed the other dir to svn/. Now, the group-write perm is set incorrectly, so I thought to correct the problem by using the (hopefully adapted) only right tool to create a repository: svnadmin. It didn't work either. So, now I'm left with only 1 way of recovering: mail you! :-) If you could set cvsroot-to-move-to-svn to read only while at it, I'll rename it back to cvsroot. Thanks in advance! bye, Erik.

2 1

[clo-devel] Fwd: Trac for usocket
by Erik Huelsmann 08 Apr '06

08 Apr '06

---------- Forwarded message ---------- From: Erik Huelsmann <ehuels(a)gmail.com> Date: Apr 8, 2006 10:26 PM Subject: Trac for usocket To: admin(a)common-lisp.net Hi! I missed Trac being set up on request, but I'd like to use it for usocket. Later on - when there's consensus and I've converted the repository - I may request Trac for cl-irc too. Thanks for providing this great service! Bye, Erik.

1 0

[clo-devel] Account Review Team
by PayPal 31 Jan '06

31 Jan '06

1 0

[clo-devel] Re: [iterate-devel] Auto-nag: iterate link verifier failed
by Andreas Fuchs 30 Jan '06

30 Jan '06

Today, <root(a)common-lisp.net> wrote: > You are being nagged on because your project's name showed up in the > nightly Checkbot run. Checkbot checks for broken links etc. This > probably means that you are either pointing to a broken link or that > someone is pointing to a broken link on your site. Or something > else, it check's a bunch of stuff. Update your webpages or you > shall be nagged again next week. > > To find out what's wrong with your webpages, please consult: > > http://common-lisp.net/checkbot/checkbot-common-lisp.net.html http://common-lisp.net/project/iterate/ * http://www.gnupg.org/ Can't connect to www.gnupg.org:80 (Bad hostname 'www.gnupg.org') www.gnupg.org WFM perfectly fine. That the link checker can't find others as well, e.g., www.cs.cmu.edu, might indicate that there is something wrong with the checker. (: It seems like the first dns server in cl.net resolv.conf file isn't responding or taking a long time to respond. Maybe that's the problem? Cheers, -- Andreas Fuchs, (http://|im:asf@|mailto:asf@)boinkor.net, antifuchs

2 1

[clo-devel] Validation warnings with clo default style.css
by Erik Huelsmann 29 Jan '06

29 Jan '06

Hi, I ran the default style.css through the w3c validation service. Although it validates as valid, there are still several warnings: when using background-color, one should also use color. Given the fact that these are *so* easy to fix, I didn't think a patch would help even a bit. Besides, I already modified the usocket style.css.... bye, Erik.

2 1

[clo-devel] Standard subversion repository layout
by Erik Huelsmann 27 Jan '06

27 Jan '06

Hi! While CVS - through its concept of modules - somewhat dictated the use of the repository, Subversion doesn't do this. Standardising on repository layout for all of clo has some advantages though: if you decide to do that, it will be possible for example to provide a standard hook script to update the project website when a change is committed for it. There are several possibilities to standardise on (taking cl-irc as an example): First: / cl-irc/ trunk/ branches/ tags/ public_html/ Second: / cl-irc/ trunk/ public_html/ branches/ tags/ Third: / trunk/ cl-irc/ public_html/ branches/ tags/ The third option is the layout you get when converting the existing cl-irc repository using cvs2svn. In my opinion, it's the least favorable, since normally tags and branches are created with copies from trunk, meaning all modules get tagged at the same time... The second option wouldn't be my favorite either, since, dist scripts would then package the website (unless special action is taken not to). I don't think websites belong in a dist tarball. The first option would be my favorite, since I don't think of a website as something needing tags and branches. This setup allows for separate tags for all modules, which is quite sane in my opinion. That's all folks! Oh, well, if you decide which you want to standardise on (remember: 3 is what you get when converting from CVS), I don't mind writing the hook. bye, Erik.

3 3

[clo-devel] Re: Commit mail setup for c-l.o
by Erik Enge 27 Jan '06

27 Jan '06

On 1/25/06, Erik Huelsmann <ehuels(a)gmail.com> wrote: > As promised, I'm mailing you about setting up a commit mailer for c-l.o. Thanks plenty! Ok, I've set up FSFS based Subversion repository for all the projects which didn't already have one and I believe I have configured the mailer and hooks correctly. Could test it (say, in usocket) and see if I've got it right? Next I have to find out a browse-through-the-web interface for Subversion. Thanks for all your help so far, Erik.

1 1

[clo-devel] Auto-nag: clo link verifier failed
by root＠common-lisp.net 23 Jan '06

23 Jan '06

You are being nagged on because your project's name showed up in the nightly Checkbot run. Checkbot checks for broken links etc. This probably means that you are either pointing to a broken link or that someone is pointing to a broken link on your site. Or something else, it check's a bunch of stuff. Update your webpages or you shall be nagged again next week. To find out what's wrong with your webpages, please consult: http://common-lisp.net/checkbot/checkbot-common-lisp.net.html Any questions? You can reach the author of this cronjob at clo-devel(a)common-lisp.net Thanks!

1 0

Re: [clo-devel] CVS commit problems
by Erik Enge 22 Jan '06

22 Jan '06

Sometime in September of 05, Rudi wrote: > > I can checkout mcclim via -d:ext:rschlatte at ... but trying to commit > gives the following message: > > cvs [server aborted]: could not open lock file `/project/mcclim/ > cvsroot/mcclim/,graphics.lisp,': Permission denied > > Does anyone know of a fix? Hello, Rudi. I'm going through the clo-devel archives and noticed that it doesn't look like anyone replied to this message. Is this still a problem for you? Thanks, Erik.

2 1

← Newer
1
...
48
49
50
51
52
53
54
...
61
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

clo-devel