> > > > > A few notes here, in case it will save someone else a few headaches. > Note that I used git-svn to do the migration locally (GitHub's automatic > SVN migration might be too simplistic for the CAS repo, depending on > branching/tagging complexity). > > A suggestion: for a migration, svn2git[1] might be a better choice than > git-svn alone. Among other things, it creates actual git tags for tags > (git-svn imports svn tags as git branches). git-svn is a good choice if > you're creating a git mirror of a subversion repo that will continue to be > updated (and used to be the only way to go at all) but nowadays svn2git > produces a cleaner result for a one-shot conversion. > > Rhett > > [1]: https://github.com/nirvdrum/svn2git > > I did try svn2git, but it seemed to trip over the same commits as git-svn, leading me to believe that svn2git used git-svn (or a *very* similar process) somewhere early in the process. But I agree that, at least on paper, svn2git should give more accurate results.
For the most part, the tutorial at http://john.albin.net/git/convert-subversion-to-git gave me pretty good guidance. -- [email protected] Key ID:7208B5B4 -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
