gfsd-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gfsd]Re: CLISP on GNU directory and GNU web pages


From: Sam Steingold
Subject: [gfsd]Re: CLISP on GNU directory and GNU web pages
Date: 04 Apr 2002 14:21:27 -0500
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2.50

People, I feel like I am talking to a wall.

There might have been a lively reaction behind the scenes to what I say,
but nobody ever got back to me regarding the questions I raised almost a
year ago (2001-07-21), and, of course, nothing has changed on the GNU
pages.  (well, an occasional e-mail from RMS with a request to do
something, CCed to me, is a nice exception, not nothing is being done!)

So, I will send this exact e-mail (automatically, if necessary) to the
above addresses (address@hidden, address@hidden,
address@hidden, address@hidden), every week, in the hope that pestering you
will change something.  Is it OK?  Is there anything else I can do?

The issues are:

1. <http://www.gnu.org/directory/lisp.html> does not mention CLISP
   (nor GCL, nor Maxima).

2. A search for "lisp" on <http://www.gnu.org/directory/index.html> does
   not find CLISP; a search for "clisp" finds nothing.

3. This last issue is just a couple of months old - nothing compared to
   the first two: <http://www.gnu.org/licenses/fdl.sgml> does not have
   "id" properties in "sect1" elements.  This is absolutely crucial
   since without these ids, HTML generators create files with generated
   names, shich screws up CVS &c.  This _is_ important.

Please note that while [2] might be a hard problem, [1] and [3] involves
a trivial additions to 2 simple files, and if you let me, the problems
would have been resolved in 10 minutes!

Thanks.

-- 
Sam Steingold (http://www.podval.org/~sds) running RedHat7.2 GNU/Linux
Keep Jerusalem united! <http://www.onejerusalem.org/Petition.asp>
Read, think and remember! <http://www.iris.org.il> <http://www.memri.org/>
will write code that writes code that writes code for food




reply via email to

[Prev in Thread] Current Thread [Next in Thread]