Hi guys, Quick reminder, the file https://github.com/MojoHaus/convert-to-git/blob/master/mojo-committers.list will be used for the conversion. For anyone inside that file *without the correct format*, git svn will stop and refuse to continue.
So, for any line in the above file, the used format will be "$currentValue < noemailprovi...@codehaus.org>" (using --authors-prog option for git svn fetch). Cheers 2015-04-12 23:11 GMT+02:00 Jörg Hohwiller <jo...@j-hohwiller.de>: > Hi, > > plan sounds great. > +1 > > do you already have a (rough) roadmap/schedule? When should we stop > working in SVN, wenn will the Git repos be available? > > Thanks > Jörg > > Am 08.04.2015 um 09:03 schrieb Baptiste Mathus: > > > > Forking the thread to focus around Git tinkering. > > > > FWIW, some of you already noticed and added their mappings (svn > > user=Git formatted user), but I created a small repo under MojoHaus org. > > > > Please contribute the missing mappings for your user id. > > > > I also did a quick and dirty svnadmin load +Git svn clone yesterday. > > The resulting (temporary) raw repository is > > here: https://github.com/MojoHaus/svnrepo-gitified-wip > > > > Here's a first draft proposal of the technical and organizational > > steps we would follow (feedback needed): > > > > 1. freeze svn (put it ro and ask for a new dump from Ben) > > 2. Import it locally > > 3. Git svn clone it with the user mappings given above (without the > > --stdlayout option) + push it to GitHub > > > > Then from this monolithic big repo, write a shell script to do the > > following: > > > > 4. For each plugin: git filter-branch to create a repo per plugin. > > 5. For site: filter-branch too > > 6. Check everything > > > > WDYT? > > > > BTW we need to PoC the site publication too and think about how to > > make it not too cumbersome with all those repos there will be. If > > someone can have a look that'd be great. > > > > > > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
