The most painless solution would be just to check in a snapshot of the hg repo into svn.
If there is a way to preserve history, then that would be better, but I don't think the history is valuable enough for anyone to spend more than a few hours looking in to it. e.g., we've lost history twice before: once in the move of wave code from our internal repositories out to Google Code, and then once again when we merged the wave-protocol-libraries repo into wave-protocol. In either case, once the appropriate mechanisms are working, we should announce that we'll do the migration a few days or a week in advance, to give contributors enough time to submit what they can. Trying to continue a patch through a repository + vcs change can be quite painful. -Dave On Wed, Feb 2, 2011 at 1:06 PM, James Purser <jamesrpur...@gmail.com> wrote: > has anyone had a look at the best way to convert from hg to svn? > > Google brings me plenty of ways to do it the other way, but nothing > helpful. > > James > > On Wed, Feb 2, 2011 at 1:03 PM, Michael MacFadden < > michael.macfad...@gmail.com> wrote: > > > Mentors, > > > > Looks like you need to set up the SVN repo. I am sure you know this, but > I > > figured out that the mentor's had to do it by reading the following > > instructions. Thanks. > > > > http://incubator.apache.org/guides/mentor.html#Set+Up+Podling > > > > ~Michael >
