APA> Why not link to these directly, where appropriate? Stephen> Partly because I didn't know about it, partly because Stephen> ChangeLogs are often hard to read if you're not Stephen> intimately familiar with the code. The people who need Stephen> the News file most need something oriented toward Stephen> important content changes. Fine with me. I just wanted to alert you to the ChangeLog-via-HTTP option. Stephen> I plan to reformat it to something more friendly, but Stephen> this will do for now. Stephen> Um, http://xemacs.sourceforge.net/xemacsweb/... doesn't Stephen> exist; xemacsweb seems to descend right off the root of Right. htdocs, the root of our website at SF, is a symlink to xemacsweb. Stephen> our hierarchy. If we move the code development to Stephen> SourceForge, are we planning to make that a separate Stephen> project? Or a module under xemacsweb? I think xemacsweb deserves to be a separate CVS module, just like xemacs and xemacs-packages are spearate modules. Opinions? This raises some questions since I would like to offer HTML versions of all XEmacs .texi sources for the stable and the development branch via http://xemacs.sourceforge.net/Documentation/ Best regards, Adrian Stephen> -- Stephen> University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Stephen> Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 Stephen> _________________ _________________ _________________ _________________ Stephen> What are those straight lines for? "XEmacs rules." -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/