On Fri, 17 May 2019, Jason Merrill wrote: > Thanks for looking into this. My feeling has been that, if we give up > on reposurgeon, there's no need to start a new conversion at all: we > can just switch the current mirror over to being the primary > repository with some minor surgery (e.g. using git filter-branch to > fix subdirectory branches). That approach will produce the least > disruption in the workflows of people already using it. Do you see a > problem with this?
I'd expect more major surgery (in particular remapping authors) if reposurgeon fails. I don't expect reposurgeon to fail. I expect even the python version of reposurgeon would work, with a few bug fixes - it's just that with day-long test cycles and hours to load a GCC repository dump into the python version, it's very hard actually to debug subtle issues with handling Subversion dumps to find out what those bugs are and fix them, which is where the Go version should help once finished, by being substantially faster. -- Joseph S. Myers jos...@codesourcery.com
