The poll for changes stuff and saving recent change entries could use more checks to make sure duplicate entries do not get saved.

This could be:

1. at the recent change save point

2. in poll for changes, programatically know which change id to start at, maybe with a hook point before pollforchanges queries the changes table.

or both. This is in event the poll for changes script has to be restarted.

Right now, it can use --since and work at a specified time interval with a cron job or run continuously as a daemon.

Version: master
Severity: normal