Hi Adrian, The reason is not that writing ChangeLog-entry makes not much fun (btw: it doesn't but with stuff like add-change-log-entry or the patcher library it is not a big deal) but is is the "modus operandi" how i managa the ECB-package in general and especially the XEmacs- version: 1. ECB has its won master upstream and ONLY this one is "developed". Has its own CVS at SourceForge etc....all bug-fixing and testing (i.e. all XEmacs testing too!) and development takes place with this upstream. 2. This upstream uses NO ChangeLog but only a NEWS file which lists at a higher level all bug-fixes and new features etc... The lack of a ChangeLog file with detailled entries for every single change has mainly historical reasons...at beginning we thought we do not need such a ChangeLog....and now we are too lazy.... ;-) 3. If a new upstream package is released (e.g. the new 1.93) then i copy all new sources of the upstream to my working-directory of the XEmacs- version of ECB. Then i build the new xemacs-package and test it if all new features and bug-fixes are also working if installed as xemacs- package. If yes then a new xemacs-version (e.g. 1.06) is ready for prerelease. You see, cause of development without a Changelog (point 1. and 2.) i have no chance to add ChangeLog-entries at step 3. And i do not want to "reproduce" what i have changed....ad all high-level descriptions about fixed bugs and new features of the new release are contained in the NEWS file which is part of the xemacs-version and is included in the package! Why should i recapitulate the entries of the NEWS file in the ChangeLog?? All informations are available. Ville and i have agreed that this approach of managing ECB as a xemacs- package is ok. Normally i can not reproduce at step 3. (see above) what changes i have made in detail and therefore i can't generate patched! Yes, sorry, it was a mistake, i will do this next time! :-) Ciao, Klaus