On Thu, 5 Dec 2019, Richard Earnshaw (lists) wrote: > Ok, this is one to keep an eye on. There are a number of anomalous commmits > at present, which Eric is working on with a new approach to replaying the SVN > data into reposurgeon. Once that is done we're hoping that this sort of > problem will go away. (of course, if it doesn't then the chances are we won't > be using reposurgeon for the conversion at all).
I think we currently have the following reposurgeon issues open for cases where the present code results in incorrect tree contents and we're hoping the new code will fix that (or make it much easier to find and fix the bugs). These are the issues that are most critical for being able to use reposurgeon for the conversion. https://gitlab.com/esr/reposurgeon/issues/167 https://gitlab.com/esr/reposurgeon/issues/171 https://gitlab.com/esr/reposurgeon/issues/172 https://gitlab.com/esr/reposurgeon/issues/178 -- Joseph S. Myers jos...@codesourcery.com
