I usually find it best to make 1 git svn clone with all the repos and then just filter-branch the hell out of that -including rewriting of roots, once for each repo.
In the case of mojo, once you get a script that works for one project it should be possible to re-apply that script in an automated fashion to the entire reposiotory. The crux is usually to be able to maintain the connection the svn while hacking with these things,so it usually pays off to keep the master git-svn repo "still attached" to svn, so it can all be re-run in a few perilous hours at some point on up-to date svn repos. And of course, even on linux it pays of to give filter-branch liberal amounts of tempfs to work with. It's definitely a few days of work to do it all. Kristian 2013/6/28 Fred Cooke <[email protected]>: > You have to subdivide the old monolithic SVN repo into the individual repos > that make sense, at the very least. Considering the sheer volume of it, it'd > be wise to either use, or create a method of pre-analysing/transferring the > entire SVN repo from day 1, and then extract each git repo from that. I'm > unsure if such a thing exists, however the alternative of analysing the > entire repo N times, once for each MOJO would take AGES. Perhaps you can do > it as a batch with some tool? Someone would have to explore this if it were > to be done. > > Aside from that obvious(?) part of it, the convert tools do non-ideal things > from a Git perspective when non-ideal things have been done in the SVN repo. > Maven related repos are riddled with deleted tags (see other threads...) and > perhaps other things(?) so will require some love to get a nice set of git > repos from. > > Long story short, it's a lot of work to do *right* and the motivation level > to move over is often not high in big group-projects, and sometimes there > are stick-in-the-muds who actively campaign against the improvement. Always > remember, change is bad, unless it involves destroying the environment for > short-term personal financial gain. :-) > > Fred. > > > On Fri, Jun 28, 2013 at 4:07 PM, Jochen Wiedmann <[email protected]> > wrote: >> >> Just asking: Does Github offer to provide an SVN mirror? Or is there any >> other way to have a mirror without too much hazzle? >> >> >> >> On Fri, Jun 28, 2013 at 9:50 AM, Fred Cooke <[email protected]> wrote: >>> >>> >>>> >>>> For GIT users there are several ways to work with SVN, so that's >>>> probably why this isn't that urgent. >>> >>> >>> That's not really a good reason not to, because: >>> >>> The SVN >> Git process isn't fast (because SVN is itself SLOW) >>> Each converter has to find motivation to bother setting this up and doing >>> it in the first place. (read, they'll just not bother most of the time) >>> Each conversion will have a different set of hashes even if the other >>> parameters are the same and thus won't be able to be collaborated between >>> effectively. >>> >>> Having a single official mirror means others can effectively work >>> together on "it" with the final result pulled back into SVN when ready and >>> then automatically pushed back to Git again. The work flow is a pain, but >>> still a lot better than suffering SVN in the first place. >>> >>> migrate > 1 official mirror (per mojo) > N unofficial mirrors/leave it >>> alone >>> >>> I'm not ignoring the work involved in mirroring, just pointing out some >>> facts. I don't think the Maven tool-set / infrastructure is 100% ready for >>> Git, to be perfectly honest. The sink or swim method may be a good way to >>> get it there, but might be painful, too. I'd certainly appreciate more Git >>> friendly behaviour, though :-) >>> >>> Fred. >>> >>>> >>>> Robert >>>> >>>> >>>> On Thu, 27 Jun 2013 21:44:33 +0200, Lennart Jörelid >>>> <[email protected]> wrote: >>>> >>>>> Folks... if anyone has an answer to this question, I would be all ears. >>>>> Can I work with GIT or Mercurial here? Onto some mirror? >>>>> If not - is there a process to distribute projects/plugins to GitHub? >>>>> >>>>> >>>>> 2013/6/25 Lennart Jörelid <[email protected]> >>>>> >>>>>> Hello all, >>>>>> >>>>>> I wonder if the Mojo project has a structured way of migrating to a >>>>>> distributed VCS (GIT, presumably, or Mercurial) for various currently >>>>>> SVN-based projects - or any policy on a 2-way mirroring between the >>>>>> two >>>>>> VCS'es. >>>>>> >>>>>> I believe distributed VCSs increase visibility and reduce complexity >>>>>> for >>>>>> donning a patch compared to the standard subversion way, particularly >>>>>> with >>>>>> the help of processes and services such as GitHub or BitBucket. >>>>>> Anything >>>>>> that can increase visibility and reduce hinders in contributing >>>>>> patches to >>>>>> projects is in itself a Good Thing. >>>>>> >>>>>> So ... is there a Git/Mercurial mirror or migration process for SVN >>>>>> projects at Codehaus? >>>>>> If so - where can I find access details? >>>>>> If not - why? >>>>>> >>>>>> -- >>>>>> >>>>>> +==============================+ >>>>>> | Bästa hälsningar, >>>>>> | [sw. "Best regards"] >>>>>> | >>>>>> | Lennart Jörelid >>>>>> | EAI Architect & Integrator >>>>>> | >>>>>> | jGuru Europe AB >>>>>> | Mölnlycke - Kista >>>>>> | >>>>>> | Email: [email protected] >>>>>> | URL: www.jguru.se >>>>>> | Phone >>>>>> | (skype): jgurueurope >>>>>> | (intl): +46 708 507 603 >>>>>> | (domestic): 0708 - 507 603 >>>>>> +==============================+ >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Using Opera's revolutionary email client: http://www.opera.com/mail/ >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>> >> >> >> >> -- >> "That's what prayers are ... it's frightened people trying to make friends >> with the bully!" >> >> Terry Pratchett. The Last Hero >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
