Hi Ryan!
I got this "message too big" moderation notice from common-lisp.net but I'll be buggered if I can remember the list moderator password. Can you maybe resend with gzip'd patches?
Hi common-lisp.net admin: I'd actually like to stop being moderator of any mailing lists since I don't follow them these days. Perhaps at ECLM I can ask around for someone to take over my neglected responsibilities :-)
Cheers, Luke
P.S. monkeys.org is a spectacular domain name, I'm jealous! I lost my beloved vegetable.org years ago.
---------- Forwarded message ---------- From: clbuild-devel-owner@common-lisp.net < clbuild-devel-owner@common-lisp.net> Date: 20 Mar 2008 21:46 Subject: clbuild-devel post from ryan@mokeys.org requires approval To: clbuild-devel-owner@common-lisp.net
As list administrator, your authorization is requested for the following mailing list posting:
List: clbuild-devel@common-lisp.net From: ryan@mokeys.org Subject: two patches: a spaces vs tabs fix in clbuild, and more projects Reason: Message body is too big: 41764 bytes with a limit of 40 KB
At your convenience, visit:
http://common-lisp.net/cgi-bin/mailman/admindb/clbuild-devel
to approve or deny the request.
---------- Forwarded message ---------- From: ryan@mokeys.org To: clbuild-devel@common-lisp.net Date: Thu, 20 Mar 2008 10:46:11 -0400 (EDT) Subject: two patches: a spaces vs tabs fix in clbuild, and more projects First, I had a problem manually adding my own repos to the projects file, and it came down to spaces vs tabs:
Breaks: adw-google\tget_darcs\shttp://... Works: adw-google\sget_darcs\shttp://...
The attached spaces-tabs.patch uses a more flexible regex when grepping the project file to support any space character.
Second, the attache more-project.patch adds some more libs to main projects file. All are cl-net projects or ediware: cl-interpol, parenscript, cl-json, rfc2109, and yaclml. I'm not sure what the criteria is used to determine whether a library goes in the projects file or the wnpp-projects file. All of these seemed pretty stable and didn't have any weirdness updating using ./clbuild update --main-projects, so I figured it'd be ok.
Thanks, Ryan
---------- Forwarded message ---------- From: clbuild-devel-request@common-lisp.net To: Date: Subject: confirm 2eefe4f6bb6fbec0f5f4e65b49b91606456c21ec If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply.