Hi ! I've just released the next version of Patcher. It's already part of the xemacs-devel CVS archive. This is a *major* version upgrade. In short, Patcher now has the ability to deal with manually written ChangeLog entries. Here's a more detailed description of the new stuff: - ChangeLog related work is controlled via the `change-logs-updating' option (values: automatic, manual, or nil). * nil means that Patcher does not handle ChangeLog files in any particular way. You can have ChangeLog entries, but Patcher simply consider ChangeLog files has random source files. * automatic means that Patcher will generate ChangeLog skeletons. This is the only behavior of preceding versions. * manual means that Patcher assumes that you have written the ChangeLog entries (manually) prior to preparing the message. - ChangeLog appearance in Patcher messages is controlled via the `change-logs-appearance' project option (values: verbatim, packed, patch, or nil) and the `change-logs-diff-command' one. * nil means that you don't want to see ChangeLog entries in the message, * verbatim means that ChangeLog entries are inserted as plain text in the message (this is the old behavior). * packed means that ChangeLog entries appear as a diff, but are packed together before the patch itself. * patch means that ChangeLog files are diff'ed as part the patch itself. For the last two cases (which are both a diff appearance), the diff command can be either the one used for the patch itself, or a special one given by the `change-logs-diff-command' project's option. - The prologue mechanism has changed: * there's a new `change-logs-prologue' project option, * there's a new `diff-prologue-function' project option. - Improvements on the LogMsg part: * the option `init-log-message' has been replaced with a more powerful `log-message-items', * see also the option `change-logs-separator', * you now have a set of interactive commands to (re)insert different LogMsg parts (namely: ChangeLog entries, compressed versions, subject line). - Improvements on the gnus mailing method: * Patcher is now able to start gnus by itself if it is not running yet see the variables `patcher-mail-run-gnus' and `patcher-mail-run-gnus-other-frame'. Next step is .... writing a real documentation :-) Enjoy ! -- Didier Verna, didier(a)lrde.epita.fr, http://www.lrde.epita.fr/~didier EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 53 14 59 47 94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 53 14 59 22 didier(a)xemacs.org