Hello Baptiste,

first of all, thanks for your efforts, mind-boggling git-vodoo :-).
One thing I noted (when inspecting the repository with SourceTree):
* When I take a look at a repository which was git from the beginning,
tags are modeled differently. Using the maven-release-plugin, they
just are attached to the commit with the message
"[maven-release-plugin] prepare release..."
* In the converted extra-enforcer-rules-wip, the tags are attached to
the commit with the message "[maven-release-plugin] copy for tag..."
and these commit are in extra branches with just one commit each.
* I do not know how to fix this, but to be consistent with future tags
I think it would be nice if we could get the tag to the "prepare
release" commit :-).

Regards
Mirko
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/


On Sat, May 2, 2015 at 7:53 AM, Baptiste Mathus <bmat...@batmat.net> wrote:
> Hi,
>
> I finally wrote a rough script yesterday that seems to work. Please review.
> https://github.com/mojohaus/convert-to-git/blob/master/convert.sh
>
> I currently declare the repo I want to migrate in a dedicated file (still
> needs to be enriched to support sandbox and weird cases, currently only
> supports trunk mojos):
> https://github.com/mojohaus/convert-to-git/blob/master/repo-infos.csv
>
> What it does currently:
>
> for each line of the csv file above
>         - create an empty local git repo
>         - find the associated svn tags in the svn repo
>         -   and create the right git-svn props
>         - git svn clone
>         - fix git/svn branches to be real Git tags
>         - by github api : create the repo under the org
>         - push them all
> end for
>
>
>
> The script just worked for the repos I declared (I added a suffix -wip to
> inform people it's not ready yet)
>
> https://github.com/mojohaus/extra-enforcer-rules-wip
> https://github.com/mojohaus/build-helper-maven-plugin-wip
>
>
> WDYT?
>
> Cheers
>
> 2015-05-01 21:59 GMT+02:00 Baptiste Mathus <bmat...@batmat.net>:
>>
>> 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 !
>
>
>
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to