>>>> "APA" == Adrian Aichner
<Adrian.Aichner(a)t-online.de> writes:
APA> I have a small patch for this. The version you sent has
APA> never been run.
Sorry about the typo, I was working on a different XEmacs and
copy/pasted via X -- the code was working in my other XEmacs.
APA> 1. Include this in release-mail-to-html.el
APA> 2. Find a name for your utility, put it in xemacsweb and have
APA> release-mail-to-html.el (require ...) it.
Sure, do what you like with it. I've had a bad weekend personally,
and am going to concentrate the next couple of days on getting a
release out incorporating many recent contributions. I don't have
time to work on it for a while; it was intended as proof of concept.
The only necessary thing is legal; I've signed assign.future so if you
add it to XEmacs, it automatically becomes copyright FSF -- don't
leave my name in the Copyright column.
I plan to clean it up eventually, I've got a bunch more code in
development for related functions. Why don't you call it
msgid-to-url.el, do s@sjt/@mtu-@/g on it, and put it in the same place
as release-mail-to-html.el. Probably it will get renamed or
incorporated in a larger library, so I don't recommend it for
xemacs-devel as it is.
What I suggest (eventually) is that the xemacs-devel package be split
into two pieces, xemacs-devel and xemacs-releng. xemacs-devel will
contain generally useful utilities, such as msg-id-to-url.el and
cvs-rw (in lib-src, I guess?). xemacs-releng will focus on stuff of
specific interest to release engineers, including most of what
currently is in xemacs-builds, my own xre.py (a reimplementation of
Martin's perl script xre), etc. I suggest this is a better place for
release-mail-to-html.el than the xemacsweb module, too.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."