git whatchanged has been shown to skip commits in some circumstances

Under some circumstances which are not known, 'git whatchanged' will fail to include commits. When this happens, FishEye will warn and attempt to proceed with indexing anyway.

We should fix this so that when one of these commits is encountered, FishEye stops processing the whatchanged output, indexes the missing commit as a single commit, and then proceeds with indexing. This will be a bit tricky to ensure that things happen in the correct order.

See linked support case for more details