Due to a miscomputation of svn commit range at startup on, the second visit for theof a SvnLoaderFromRemoteDump, fails.
this had a range of svn commit [1-0]. That in turn made the svn loader resolve an
unknown revision number. This should have been an uneventful visit from the start.
This commit fixes itIt should be caught into an uneventful visit as nothing new happened in between visits.
Related to T3622