Hi again,
Daniel Pocock wrote:
One other factor I didn't mention in the original email, some of the
branches have been renamed/moved within the SVN repo - is that a problem for
git-svn?
Yes, I think so.
One compromise I have thought about would be just extracting trunk, and
forgetting about the branches, and manually tagging the official releases
(as there were very few of them, this is quick)
Just use contrib/svn-fe in that case: it's really quick and
lightweight. You can then filter-branch the history and pull out
branches by hand.
However, based on the errors/warnings, is it possible that there is any
corruption in the gitified version of trunk (or the history of trunk)?
No corruption is possible on the Git side of things- it has
cryptographic hashes for everything.
Ram