Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369839 - Please provision Gemini.JPA with a git repo
Summary: Please provision Gemini.JPA with a git repo
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Git (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-26 12:07 EST by Michael Keith CLA
Modified: 2014-02-21 11:39 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Keith CLA 2012-01-26 12:07:36 EST
We would like to start converting from svn to git.

Thanks!

-Mike
Comment 1 Eclipse Webmaster CLA 2012-01-27 21:50:21 EST
Ok, I've created /gitroot/jpa .  You can init the repo with:

initrepo /gitroot/jpa/org.eclipse.jpa.reponame.git

-M.
Comment 2 Michael Keith CLA 2012-01-28 10:35:06 EST
(In reply to comment #1)
> Ok, I've created /gitroot/jpa .  You can init the repo with:
> 
> initrepo /gitroot/jpa/org.eclipse.jpa.reponame.git
> 
> -M.

Er, that should be org.eclipse.gemini.jpa.

Also, what is the best way to execute the initrepo command if I don't have shell privs?
Comment 3 Denis Roy CLA 2012-01-28 16:16:31 EST
To be consistent with the other gemini projects, I've renamed /gitroot/jpa to /gitroot/gemini.jpa.

You can run the initrepo command from the restricted shell.  If you'd like to perform the conversion yourself, we can provision you (or someone on your team) a shell.  We can also do the migration for you if you'd like.

Please confirm...
Comment 4 Michael Keith CLA 2012-01-29 22:00:39 EST
If you can do the migration that would be even sweeter.
(I'm not one to turn down offers of assistance :-)

So you can just dump all the code from our svn into git? What happens to the history? I guess we just keep the svn around for that? 
I have held off developing on our next release, so now would be a good time to cut over.

Thanks,
-Mike
Comment 5 Michael Keith CLA 2012-01-30 16:35:11 EST
Can you let me know the particulars of what you are offering to do, and the parameters of what I should or should not be doing? For example, when should I stop changing code in my current SVN?
Comment 6 Denis Roy CLA 2012-01-31 11:55:35 EST
We can import (as best we can) your SVN history into your new Git repo.  If you want things structured differently, that's another story.

Your best bet is to tell us what you'd like for us to do, and suggest a day where you can afford to not write to SVN.  On that day, we'll make your SVN read-only and import it.

We can also do a quick trial run -- we can import SVN now into your git repo, you can try it out, and we can start all over and do the real thing another day.
Comment 7 Michael Keith CLA 2012-01-31 11:59:34 EST
That sounds great!

I can agree not to write to the SVN for today if you have the time to start it going. Shouldn't take very long as the project is not that big. Let me know when it is done and I will take a look at the results. Thanks!
Comment 8 Eclipse Webmaster CLA 2012-02-01 15:01:38 EST
I've created /gitroot/gemini.jpa/org.eclipse.gemini.jpa.git and imported your SVN repo.  Let me know if there are any problems.

-M.
Comment 9 Michael Keith CLA 2012-02-03 16:33:06 EST
Things look good to me so far.

Thanks very much for your help!

-Mike
Comment 10 Denis Roy CLA 2014-02-21 11:39:33 EST
Closing as per previous comments.