It looks like an indirect consequence of history parsing problems when there are whitespaces in file and/or module names.

When such a file path is badly parsed, version info can't be retrieved (log message, timestamp, user, etc). The default for such a case is to consider the file to belong to a different changeset, hence the multiple messages for a single commit. I still consider this to be the 'safest' default since it only generate extra reports instead of false reports (ie. wrong aggregations of file in the same changeset). And actually the problem is really in history parsing, not in changeset detection.

For the history parsing part, the best we can do is have a new path to parse directly from CVSROOT/history when $cvsroot is local. It is feasible, although I'd like to do it right, ie. without clobbering parse_history() which is already quite touchy.

I expect to fix this soon (~1 week).