> On May 17, 2019, at 2:06 AM, Joseph Myers <jos...@codesourcery.com> wrote: > > On Tue, 14 May 2019, Maxim Kuvyrkov wrote: > >> The scripts convert svn history branch by branch. They rely on git-svn >> on convert individual branches. Git-svn is a good tool for converting >> individual branches. It is, however, either very slow at converting the >> entire GCC repo, or goes into infinite loop. > > I think git-svn is in fact a bad tool for repository conversion when the > history is nontrivial (for the reasons that have been discussed at length > in the past),
I agree with this. However, with git -- we don't need to force ourselves to convert the whole history in one go; git-svn seems to be doing a good job at converting branch at a time. > and we should convert with reposurgeon. If reposurgeon works -- great, let's convert with it. It's good to have two independent tools so that we can compare and sanity check the results; from the top of my head: 1. number of merges should match on all branches, 2. changed files should match for all revisions. What I want to avoid is delaying the switch to git. > > ESR, can you give an update on the status of the conversion with > reposurgeon? You said "another serious attack on the repository > conversion is probably about two months out" in > <https://gcc.gnu.org/ml/gcc/2018-12/msg00112.html>. Is it on target to be > done by the time of the GNU Tools Cauldron in Montreal in September? > > And, could you bring git://thyrsus.com/repositories/gcc-conversion.git up > to date with changes since Jan 2018, or push the latest version of that > repository to some other public hosting location? That repository > represents what I consider the collaboratively built consensus on such > things as the desired author map (including handling of the ambiguous > author name), which directories represent branches and tags, and what tags > should be kept or removed - but building up such a consensus and keeping > it up to date over time (for new committers etc.) requires that the public > repository actually reflects the latest version of the conversion > machinery, day by day as the consensus develops. Review of that > repository will be important for reviewing the details of whether the > conversion is being done as desired - the details of the machinery will > help suggest things to spot-check in a converted repository. -- Maxim Kuvyrkov www.linaro.org
