Re: Tramp changelog entries messes up lisp/ChangeLog

[kai.grossjohann@uni-duisburg.de (Kai Großjohann)]

Richard Stallman <rms@gnu.org> writes:

>     This is sometimes hard to do, especially when the original sequence
>     of log entries is long.  This is because the original log frequently
>     mentions multiple changes to the same function; merging them all into
>     a single entry for each function is time-consuming and might actually
>     lose information (e.g., when changes are backed up).
>
> I find this makes it easier to grasp the changes overall.
> It is worth doing.

I've now looked and tried to condense entries such that the ChangeLog
reports the overall change from beginning to end, without
intermediary steps.

I hope I didn't miss anything.
-- 
A turnip curses Elvis