PLEASE migrate Subversion history into Git

[ymartin59]

Hello

Looking for tags, I just discover Subversion history has not been migrated.

I expect it is obvious to any developer that full commit history for such a project is a "must-have" when patching, bug-fixing and tackle regression issues.

Please use either "git svn" or svn-all-fast-export to migrate full Subversion history into a clean and complete Git repository.

I may help if needed, as far as I may grab a dump with "svn rdump".

Regards
Yves

[dibgraversen]

We have a copy of the old SVN repository, but unfortunately the structure of that codebase does not match the codebase we are working on, so when we tried to create a repository based on the SVN dump, and then "merge" the actual codebase into it, it was basically a delete of all existing files, and a create of all the new files.

We could upload the SVN dump file (it is huge, 500+ MB in size), for those interested.

[ymartin59]

@dibgraversen "svn-all-fast-export" tool allows to specify rules with custom path mapping to generate Git repository, so I should be able to propose rather a proper migration result, even after few trials-and-errors processing.

I cannot "accept" to loose history of such "important" source code so I will provide (as much as required) help to get it right.

My last migrated Subversion repository were 13 GiB large (I am currently processing many repositories at work)... so I do not consider yours so "huge".

Let me know where you upload the SVN dump and Subversion structure to split into one or many Git repositories. To get it right, tool also requires Subversion username mapping to "full name < email@address >" for commits' author migration to Git.

[dibgraversen]

Hi Martin.

If you could drop me a mail at bsg@digital-identity.dk, we can find a way to send the file to you, and figure out what is needed to get the dump into github.

[ymartin59]

@dibgraversen Here is the result of migration I did with svn-fast-all-export https://github.com/ymartin59/oiosaml.java-from-subversion

I have created fake email addresses for most Subversion authors identifiers. This may be improved and migration run again to correct them.

Notice "git notes" contain Subversion path location and revision for each Git commit (but are not shown by GitHub interface)

The "oiosaml2" branch is disconnected from "master" as it has not been created with a "svn copy" in Subversion repository but I plan to re-connect it, included other recent commits in this Git repository.

Then output of "git blame" should show us that most history has been kept/retrieved in that operation.

[ymartin59]

@dibgraversen Job is not over yet to be published. And because it is open source and IP copyright matters, I would like you to review and maybe contact authors of code, to get their agreement for using a better "name" and email address (moreover if they have a GitHub account) than the temporary author information I have use to test migration (JRE, CAS, KFR, BBG, USK ,SPE):

git shortlog -e -s -n
   204  JRE <jre@users.noreply.github.com>
    32  mollekas <mollekas@users.noreply.github.com>
    29  CAS <cas@schultz.dk>
    26  KFR <kfr@users.noreply.github.com>
    11  BBG <BBG@users.noreply.github.com>
     3  BGraversen <BGraversen@users.noreply.github.com>
     3  mkhansen <mkhansen@users.noreply.github.com>
     2  USK <usk@trifork.com>
     1  SPE <spe@schultz.dk>

Thank you in advance for your help to improve this part of the migration process.