When I switched Open-MX and KNEM from SVN to GIT, I basically just pushed my git-svn clone. But I had to manually convert some svn tags/branches. IIRC, the main reason is that git-svn has a strange way to name svn branches in git.
We may also have to pass --authors-file to git svn clone so that SVN logins are converted into proper git author names. Brice Le 04/06/2013 12:14, Jeff Squyres (jsquyres) a écrit : > Ok. This is kinda what I assumed your response would be. :-) > > Let me talk to Dave Goodell later today, who just recently went through > converting MPICH from SVN -> Git, and see what kinds of things we need to do > to get the ball rolling here, and what kinds of dragons we should expect to > encounter along the way. > > > On Jun 3, 2013, at 11:17 PM, Brice Goglin <brice.gog...@inria.fr> wrote: > >> +1000 !!!!! >> I already use git-svn for most of my hwloc work. But I still need svn for >> backports, and that wastes a lot of my time. >> Brice >> >> >> "Jeff Squyres (jsquyres)" <jsquy...@cisco.com> a écrit : >> We're having a discussion (again :-) ) about moving OMPI to a DVCS. >> >> The short conclusion of the long conversation is: the OMPI dev community >> would be much more comfortable moving to a DVCS if they could see some >> success with other OMPI projects (e.g., hwloc and/or MTT). >> >> Would hwloc be interested in moving to git? This would mean: >> >> 1. converting the existing svn to git >> --> including all historical log messages that refer to "rXXXX" >> 2. converting the existing trac to git >> --> including all trac tickets, comments, and wiki pages that refer to >> "rXXXX" >> >> The OMPI devs -- who are mostly unfamiliar with git -- would like to see >> some close-to-home successes with git over a period of time that don't >> require heavy administrative maintenance over time (one of the pushback >> issues was that some organizations have hired full-time people to >> maintain/fix git repositories when they break/become unusable). >> >> >> Interested? >
