Joseph Myers <jos...@codesourcery.com>:
> And here are corresponding lists of tags where the commit cvs2svn
> generated for the tag should be reparented.
Make that issue 2, please. Also, open an issue 3 about how you want those
mid-branch deletes handled. I agree that the right thing is just to nuke
them, but I have a lot of plates in the air right now...
Also please open reposurgeon issues about the svnmerge properties and the
missing documentation. I might get to the svnmerge thing today, it
should be a trivial tweak.
The repository comparison is still grinding. It has turned up some
content mismatches, fewer than last time, most in trunk/libgo.
The reason for the "fewer" is that the Go version has learned how to
correctly handle a corner case the Python did not - tag/branch delete
followed by a recreation at a different root point. That's why this
is commented out in the lift script:
# Squash accidental trunk deletion and recreation.
# Should no longer be needed due to branch recoloring.
#<130803.1>,<138077>,<184996.1> squash
I used to have to find defects like that by hand and patch them. Now
there's a recoloring phase where branches and tags with multiple
creations are handled by renaming all but the last such branch in each
clique to a unique nonce name. This makes all the results from branch
copies come out right, and none of the nonce names are ever visible in
the final conversion.
I'll go dive into the defect analysis now.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
