Fixed another instance of the same logic error in channel-log updating

I forgot that the same buggy algorithm was also in TruncateEncodedChangeLog.

For #158 (possibly a fix but I'm not sure)