SL Baur writes: sb> They have been useful to me letting me know which packages need new binary sb> kits built. That's not going to matter when there's a method for sb> developers to have their packages rebuilt (hopefully) without XEmacs sb> maintainer intervention. But they're still useful in the sense seeing sb> entries appear on freshmeat is useful. sb> As to log messages, I haven't bothered with them in the core because the sb> ChangeLogs and CHANGES-beta carry all change information and I've been the sb> only one doing commits[1]. I'm all for some kind of distribution of commit sb> info and log entries and I believe the more light we shine on them, the sb> better the messages will become. Just to add another argument, they are usefull for people sending patches as well, especially when several people happen to work on the same piece of code at the same time, about unrelated topics (this just happened between me and Hrvoje last friday): if you detect a patch checkin, better to send a patch against the latest version in the archive. If you don't, maybe a patch summarizing both is better then. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19