Community
Participate
Working Groups
The Linux Tools project would like to migrate to git. Migration timeline - as soon as possible - we've discussed it as a community [1] Mapping SVN->Git - we will merge our repositories into two (see below) so archiving of our SVN repository would be appreciated Existing code - Andrew has merged our various SVN repositories into one git repository and we will use that repository (mirrored here for the time being: https://github.com/overholt/org.eclipse.linuxtools) - once SVN is frozen for migration, Andrew can get any changes between the previous snapshot he used and then and cherry-pick them over to the new repository - one exception to this is eclipse-build which will remain its own repository - see below for desired structure Desired git repo structure: Repo #1 of 1: org.eclipse.linuxtools.git Description: Eclipse tools for Linux developers and distributors Repo #2 of 2: org.eclipse.linuxtools.eclipse-build.git Description: Eclipse SDK build harness for Linux distributions I will CC all committers. [1] http://dev.eclipse.org/mhonarc/lists/linuxtools-dev/msg00695.html http://dev.eclipse.org/mhonarc/lists/linuxtools-dev/msg00723.html http://dev.eclipse.org/mhonarc/lists/linuxtools-dev/msg00769.html
Are you asking for me to import your 'current' SVN repo into Git, or to import your GitHub repo into a Git repo here at Eclipse? If it's the latter then I suspect that will require getting EMO and EMO Legal signoff. But if your going to import the data from your SVN repo(@Eclipse), then I can 'freeze' it now, and create a location for you in our /gitroot, and you can init your repos and import the data however you'd like. -M.
(In reply to comment #1) > Are you asking for me to import your 'current' SVN repo into Git, or to import > your GitHub repo into a Git repo here at Eclipse? Sorry, I should have been more clear. I'd like you to archive the current SVN repo and I'll import the SVN repo into git myself. Freezing it today/tonight is probably fine. I'm not in direct contact with the committers individually but I imagine they will either re-try and give up for today or read their email and see that it's frozen :) If you could tell me when you'll freeze it, I'll send out an email advising people of it.
Really any time to freeze is okay since I don't imagine it will take too long to do the switch over (I'll scp the git repo to dev.eclipse.org now to cut down that time).
Ok, I'm still confused. In comment 2 you're saying: > ... and I'll import the SVN repo into git myself. But then in comment 3: > ... I'll scp the git repo to dev.eclipse.org .. One sounds like you plan to use Eclipse.org hardware to convert/import the repo as it currently stands in SVN(@Eclipse) to Git(@Eclipse) which is fine. The second sounds like your going to upload a clone/copy of your github repo to us, which is a problem. I'm trying to arrange a meeting between EMO,EMO Legal and Webmaster to discuss the whole 'upload' scenario. I'll let you know when we've got an answer. -M.
(In reply to comment #4) > Ok, I'm still confused. Sorry :) > In comment 2 you're saying: > > > ... and I'll import the SVN repo into git myself. I meant I've already done so (see below). > But then in comment 3: > > > ... I'll scp the git repo to dev.eclipse.org .. I've joined our multiple SVN repositories into one. I've done this on Red Hat hardware. It took some time but I guess if it comes down to it, I can reproduce it on Eclipse hardware. > The > second sounds like your going to upload a clone/copy of your github repo to us, > which is a problem. Sorry, I should have been more clear in the beginning. Let's call the various existing SVN repos A, B, C, ..., Q. I have joined them into one git repository which we'll call 'Z'. I did this joining on Red Hat hardware. I then copied 'Z' to github for other Linux Tools committers to comment on. I plan to upload the original 'Z' directly from Red Hat hardware to Eclipse hardware. > I'm trying to arrange a meeting between EMO,EMO Legal and Webmaster to discuss > the whole 'upload' scenario. I'll let you know when we've got an answer. Thanks. Please let me know if I can clarify any of the above.
One thing that perhaps incorrectly led me to believe I could do the merging and conversion on non-Eclipse hardware was this: http://wiki.eclipse.org/Git/Migrating_to_Git#Using_svn2git_on_a_remote_server Also, when I last tried, svn2git wasn't available on either build.eclipse or dev.eclipse.
Created attachment 189616 [details] script to automate as much as possible of the svn to git conversion for Linux Tools For transparency's sake and to avoid any legal ambiguity, I think I'd like to re-do this work on Eclipse hardware. The attached script is everything that I can automate. I will do the merging and cleanup on the results of that and publish from there. This script requires the following to be installed: http://github.com/nirvdrum/svn2git http://search.cpan.org/~book/Git-FastExport-0.07/script/git-stitch-repo Please let me know if this is an acceptable course of action. Thanks.
Created attachment 189617 [details] script to automate as much as possible of the svn to git conversion for Linux Tools
Ok, I've just finished the meeting with EMO and EMO Legal and it looks like we're going to review these sort of requests case by case in future. In your case, since you're a committer(and PL) in 'good standing', as long as you have done the cleanup/conversion yourself on either your hardware or ours, and have made sure that any updates have gone(are going) through the IP process then you're all set. As such I've created /gitroot/linuxtools, you can init your repos in there and upload your conversions. I'll 'freeze' your SVN repo at 4:30pm(EST). -M.
Thanks, Matt! Could you please put an SVN dump in my ~ on dev.eclipse once you've frozen the repo?
Ok I've created linuxtools.svn.dump.gz in your home dir. -M.
Our two repositories are up. They can be seen on the web here: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/ http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.eclipse-build.git/ I've verified that Git master matches the contents of the various SVN trunks so you can freeze the SVN repository at your earliest convenience, Matt (if it's not already frozen). Thanks for your help getting this done so painlessly!
I've removed the 'w' flag in the auth file and the HTTPS access, so it should be pretty frozen. I'll wait for a few months and then remove the SVN data. As you've got the new Git repos setup I'll close this bug. -M.
