Justin Johnson wrote on Thu, Mar 01, 2012 at 08:28:20 -0600: > To make sure I understand the issue, should I be concerned about the > repositories and our ability to reproduce the history or recover from any > corruption that this bug may have caused?
The only known (and predicted) effect of the error is that some revisions are wrongly skipped during a backward history walk --- such as 'log -r HEAD:0' does. Creating an svnsync mirror is enough to fix the issue. (There is no need to check the mirror, even: if the mirror is written to by a 1.7 server (or a 1.7 svnsync over file://), the normal validation that Jason's error logs show will be done automatically.)
