Re: migrating some code to Git

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: migrating some code to Git

dejan2609
Count me in (for both actual migration and related tasks).

My weapon of choice for SVN -->>GIT would be: https://github.com/nirvdrum/svn2git (I managed to move dozen of repos few years ago).

Regards,
Dejan

On 2017-10-04 01:48, Hervé BOUTEMY <[hidden email]> wrote:

> I'd like to work on Plugin Tools with git
>
> While at it, looking at our plan [1], I see we have a few other components
> that are ready to migrate:
> - Doxia core
> - Doxia Sitetools
> - Enforcer
> - Jxr
> - Plugin Tools
> - Release
>
> What checks are required before switching these 6 components?
> Any volunteer?
>
> Regards,
>
> Hervé
>
> [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: migrating some code to Git

Hervé BOUTEMY
great, thank you for your help

in fact, AFAIK, Apache has already automatic svn2git exports [1] that are then
mirrored to github.
Then we already have:
- https://github.com/apache/maven-doxia/
- https://github.com/apache/maven-doxia-sitetools/
- https://github.com/apache/maven-enforcer/
- https://github.com/apache/maven-jxr/
- https://github.com/apache/maven-plugin-tools/
- https://github.com/apache/maven-release/

I suppose these could be the natural targets.
But I don't really see what checks to do on these.

I suppose that once we are convinced this content is ok, we can ask infra to
switch these to the canonical source (and disable the svn2git exports)

Do you see any issue in these repos?

Regards,

Hervé

[1] http://git.apache.org/

Le jeudi 5 octobre 2017, 11:45:23 CEST Dejan Stojadinovic a écrit :

> Count me in (for both actual migration and related tasks).
>
> My weapon of choice for SVN -->>GIT would be:
> https://github.com/nirvdrum/svn2git (I managed to move dozen of repos few
> years ago).
>
> Regards,
> Dejan
>
> On 2017-10-04 01:48, Hervé BOUTEMY <[hidden email]> wrote:
> > I'd like to work on Plugin Tools with git
> >
> > While at it, looking at our plan [1], I see we have a few other components
> > that are ready to migrate:
> > - Doxia core
> > - Doxia Sitetools
> > - Enforcer
> > - Jxr
> > - Plugin Tools
> > - Release
> >
> > What checks are required before switching these 6 components?
> > Any volunteer?
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: migrating some code to Git

Hervé BOUTEMY
I wrote a little shell script to check differences between tags in svn and git
checkout
the only differences I found for the 6 git repos are:
1. empty dirs (which exist in svn but are pruned in git)
2. one strage case in enforcer-1.2 where a few files seem to have newlines
issues

to me, this can be safely ignored

if nobody objects, in 72h, I'll create INFRA jira issue to switch following 6
components from svn to the current git mirror:
- Doxia core
- Doxia Sitetools
- Enforcer
- Jxr
- Plugin Tools
- Release


Regards,

Hervé

Le samedi 7 octobre 2017, 04:47:32 CEST Hervé BOUTEMY a écrit :

> re-reading our migration process documentation [1], I see "check especially
> behaviour on checking out tag"
>
> I suppose that we could compare content between git checkout and svn
> checkout for HEAD and every past release
>
> did somebody prepare a shell script for that?
>
> Regards,
>
> Hervé
>
> [1] https://cwiki.apache.org/confluence/display/MAVEN/Git
> +Migration#GitMigration-Migrationprocessdescription
>
> Le vendredi 6 octobre 2017, 00:34:11 CEST Hervé BOUTEMY a écrit :
> > great, thank you for your help
> >
> > in fact, AFAIK, Apache has already automatic svn2git exports [1] that are
> > then mirrored to github.
> > Then we already have:
> > - https://github.com/apache/maven-doxia/
> > - https://github.com/apache/maven-doxia-sitetools/
> > - https://github.com/apache/maven-enforcer/
> > - https://github.com/apache/maven-jxr/
> > - https://github.com/apache/maven-plugin-tools/
> > - https://github.com/apache/maven-release/
> >
> > I suppose these could be the natural targets.
> > But I don't really see what checks to do on these.
> >
> > I suppose that once we are convinced this content is ok, we can ask infra
> > to switch these to the canonical source (and disable the svn2git exports)
> >
> > Do you see any issue in these repos?
> >
> > Regards,
> >
> > Hervé
> >
> > [1] http://git.apache.org/
> >
> > Le jeudi 5 octobre 2017, 11:45:23 CEST Dejan Stojadinovic a écrit :
> > > Count me in (for both actual migration and related tasks).
> > >
> > > My weapon of choice for SVN -->>GIT would be:
> > > https://github.com/nirvdrum/svn2git (I managed to move dozen of repos
> > > few
> > > years ago).
> > >
> > > Regards,
> > > Dejan
> > >
> > > On 2017-10-04 01:48, Hervé BOUTEMY <[hidden email]> wrote:
> > > > I'd like to work on Plugin Tools with git
> > > >
> > > > While at it, looking at our plan [1], I see we have a few other
> > > > components
> > > > that are ready to migrate:
> > > > - Doxia core
> > > > - Doxia Sitetools
> > > > - Enforcer
> > > > - Jxr
> > > > - Plugin Tools
> > > > - Release
> > > >
> > > > What checks are required before switching these 6 components?
> > > > Any volunteer?
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: migrating some code to Git

Arnaud Héritier
+1

Can you share the script ?

On Sat, Oct 7, 2017 at 12:32 PM, Hervé BOUTEMY <[hidden email]>
wrote:

> I wrote a little shell script to check differences between tags in svn and
> git
> checkout
> the only differences I found for the 6 git repos are:
> 1. empty dirs (which exist in svn but are pruned in git)
> 2. one strage case in enforcer-1.2 where a few files seem to have newlines
> issues
>
> to me, this can be safely ignored
>
> if nobody objects, in 72h, I'll create INFRA jira issue to switch
> following 6
> components from svn to the current git mirror:
> - Doxia core
> - Doxia Sitetools
> - Enforcer
> - Jxr
> - Plugin Tools
> - Release
>
>
> Regards,
>
> Hervé
>
> Le samedi 7 octobre 2017, 04:47:32 CEST Hervé BOUTEMY a écrit :
> > re-reading our migration process documentation [1], I see "check
> especially
> > behaviour on checking out tag"
> >
> > I suppose that we could compare content between git checkout and svn
> > checkout for HEAD and every past release
> >
> > did somebody prepare a shell script for that?
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git
> > +Migration#GitMigration-Migrationprocessdescription
> >
> > Le vendredi 6 octobre 2017, 00:34:11 CEST Hervé BOUTEMY a écrit :
> > > great, thank you for your help
> > >
> > > in fact, AFAIK, Apache has already automatic svn2git exports [1] that
> are
> > > then mirrored to github.
> > > Then we already have:
> > > - https://github.com/apache/maven-doxia/
> > > - https://github.com/apache/maven-doxia-sitetools/
> > > - https://github.com/apache/maven-enforcer/
> > > - https://github.com/apache/maven-jxr/
> > > - https://github.com/apache/maven-plugin-tools/
> > > - https://github.com/apache/maven-release/
> > >
> > > I suppose these could be the natural targets.
> > > But I don't really see what checks to do on these.
> > >
> > > I suppose that once we are convinced this content is ok, we can ask
> infra
> > > to switch these to the canonical source (and disable the svn2git
> exports)
> > >
> > > Do you see any issue in these repos?
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1] http://git.apache.org/
> > >
> > > Le jeudi 5 octobre 2017, 11:45:23 CEST Dejan Stojadinovic a écrit :
> > > > Count me in (for both actual migration and related tasks).
> > > >
> > > > My weapon of choice for SVN -->>GIT would be:
> > > > https://github.com/nirvdrum/svn2git (I managed to move dozen of
> repos
> > > > few
> > > > years ago).
> > > >
> > > > Regards,
> > > > Dejan
> > > >
> > > > On 2017-10-04 01:48, Hervé BOUTEMY <[hidden email]> wrote:
> > > > > I'd like to work on Plugin Tools with git
> > > > >
> > > > > While at it, looking at our plan [1], I see we have a few other
> > > > > components
> > > > > that are ready to migrate:
> > > > > - Doxia core
> > > > > - Doxia Sitetools
> > > > > - Enforcer
> > > > > - Jxr
> > > > > - Plugin Tools
> > > > > - Release
> > > > >
> > > > > What checks are required before switching these 6 components?
> > > > > Any volunteer?
> > > > >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+
> Migration
> > > > >
> > > > > ------------------------------------------------------------
> ---------
> > > > > To unsubscribe, e-mail: [hidden email]
> > > > > For additional commands, e-mail: [hidden email]
> > > >
> > > > ------------------------------------------------------------
> ---------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
Reply | Threaded
Open this post in threaded view
|

Re: migrating some code to Git

Hervé BOUTEMY
In reply to this post by Hervé BOUTEMY
jira issue created:
https://issues.apache.org/jira/browse/INFRA-15253

Regards,

Hervé

Le samedi 7 octobre 2017, 12:32:00 CEST Hervé BOUTEMY a écrit :

> I wrote a little shell script to check differences between tags in svn and
> git checkout
> the only differences I found for the 6 git repos are:
> 1. empty dirs (which exist in svn but are pruned in git)
> 2. one strage case in enforcer-1.2 where a few files seem to have newlines
> issues
>
> to me, this can be safely ignored
>
> if nobody objects, in 72h, I'll create INFRA jira issue to switch following
> 6 components from svn to the current git mirror:
> - Doxia core
> - Doxia Sitetools
> - Enforcer
> - Jxr
> - Plugin Tools
> - Release
>
>
> Regards,
>
> Hervé
>
> Le samedi 7 octobre 2017, 04:47:32 CEST Hervé BOUTEMY a écrit :
> > re-reading our migration process documentation [1], I see "check
> > especially
> > behaviour on checking out tag"
> >
> > I suppose that we could compare content between git checkout and svn
> > checkout for HEAD and every past release
> >
> > did somebody prepare a shell script for that?
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git
> > +Migration#GitMigration-Migrationprocessdescription
> >
> > Le vendredi 6 octobre 2017, 00:34:11 CEST Hervé BOUTEMY a écrit :
> > > great, thank you for your help
> > >
> > > in fact, AFAIK, Apache has already automatic svn2git exports [1] that
> > > are
> > > then mirrored to github.
> > > Then we already have:
> > > - https://github.com/apache/maven-doxia/
> > > - https://github.com/apache/maven-doxia-sitetools/
> > > - https://github.com/apache/maven-enforcer/
> > > - https://github.com/apache/maven-jxr/
> > > - https://github.com/apache/maven-plugin-tools/
> > > - https://github.com/apache/maven-release/
> > >
> > > I suppose these could be the natural targets.
> > > But I don't really see what checks to do on these.
> > >
> > > I suppose that once we are convinced this content is ok, we can ask
> > > infra
> > > to switch these to the canonical source (and disable the svn2git
> > > exports)
> > >
> > > Do you see any issue in these repos?
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1] http://git.apache.org/
> > >
> > > Le jeudi 5 octobre 2017, 11:45:23 CEST Dejan Stojadinovic a écrit :
> > > > Count me in (for both actual migration and related tasks).
> > > >
> > > > My weapon of choice for SVN -->>GIT would be:
> > > > https://github.com/nirvdrum/svn2git (I managed to move dozen of repos
> > > > few
> > > > years ago).
> > > >
> > > > Regards,
> > > > Dejan
> > > >
> > > > On 2017-10-04 01:48, Hervé BOUTEMY <[hidden email]> wrote:
> > > > > I'd like to work on Plugin Tools with git
> > > > >
> > > > > While at it, looking at our plan [1], I see we have a few other
> > > > > components
> > > > > that are ready to migrate:
> > > > > - Doxia core
> > > > > - Doxia Sitetools
> > > > > - Enforcer
> > > > > - Jxr
> > > > > - Plugin Tools
> > > > > - Release
> > > > >
> > > > > What checks are required before switching these 6 components?
> > > > > Any volunteer?
> > > > >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
> > > > >
> > > > > --------------------------------------------------------------------
> > > > > -
> > > > > To unsubscribe, e-mail: [hidden email]
> > > > > For additional commands, e-mail: [hidden email]
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]