Community
Participate
Working Groups
Please migrate the CVS at dev.eclipse.org:/cvsroot/modeling/org.eclipse.emf/org.eclipse.emf.eef to a new git repository. The repository layout should remain the same as it is in CVS. Webmasters can feel free to start the import now. We're fine with a plain cvsimport taking the history with us. we will use the cvs until the final release of EEF 1.1 ( juno ), please tell me if it is to sson to migrate ? Thanks a lot!
Ok, I've created /gitroot/eef/org.eclipse.eef.git and imported your CVS data into it. At this point if you're happy with the Git repo, you'll have to manually keep it in sync with CVS(if you plan to continue using CVS). Beyond that I need to know when to mark your CVS as read-only. -M.
Thanks, i will see if the Git repo is good, and maintain it until the EEF 1.1 release. Stay tuned for readonly cvs :)
Hi, i played a it with the repo and it seems ok. i will synchronize manually the code from CVS to it until next release. one point i missed about the creation of the repo is the description.. how can i change it ? could I ? if no, is it possible to change it to : "EEF git repository" ? Cheers,
You can edit the /gitroot/eef/org.eclipse.eef.git/description file (by logging into git.eclipse.org), or you can use sftp to upload a replacement. I've made the requested changes. -M.
Good to know ! thanks again.
(In reply to comment #1) > Ok, I've created /gitroot/eef/org.eclipse.eef.git and imported your CVS data > into it. > > At this point if you're happy with the Git repo, you'll have to manually keep > it in sync with CVS(if you plan to continue using CVS). > > Beyond that I need to know when to mark your CVS as read-only. > > -M. Hi, With the EEF 1.1 release for juno done, we are good to move to git definitively. We've made some little corrections between the initial import and now. can you re-import the CVS history and mark it readonly ? Also, how can i ask to mirror the git repository to github ?
(In reply to comment #6) > We've made some little corrections between the initial import and now. can you > re-import the CVS history and mark it readonly ? Just to be clear, this 'new' import will replace your current git repo, and any changes you've made to your existing git repo will be lost(I'll re-use the description file) > Also, how can i ask to mirror the git repository to github ? I've added Wayne to the CC list as he seems to know how to get this going. -M.
(In reply to comment #6) > Also, how can i ask to mirror the git repository to github ? Make sure that the sourcerepository entry in the project metadata is correct. The GitHub folks periodically update our mirrors. It's a manual process that takes a little time, so we don't do it on demand.
(In reply to comment #8) > (In reply to comment #6) > > Also, how can i ask to mirror the git repository to github ? > > Make sure that the sourcerepository entry in the project metadata is correct. > The GitHub folks periodically update our mirrors. It's a manual process that > takes a little time, so we don't do it on demand. according to http://www.eclipse.org/projects/project.php?id=modeling.emft.eef, source repository points to : /cvsroot/modeling/org.eclipse.emf/org.eclipse.emf.eef /gitroot/eef/org.eclipse.eef.git
(In reply to comment #7) > (In reply to comment #6) > > > We've made some little corrections between the initial import and now. can you > > re-import the CVS history and mark it readonly ? > > Just to be clear, this 'new' import will replace your current git repo, and any > changes you've made to your existing git repo will be lost(I'll re-use the > description file) > yep, we are aware of that, this will erase any modification we made on git repo.
Ok, I've re-run the import and have replaced the old git repo with the new one. I've also marked your CVS repo read-only. -M.
(In reply to comment #11) > Ok, I've re-run the import and have replaced the old git repo with the new one. > I've also marked your CVS repo read-only. > > -M. verified, working like a charm. bye bye, CVS !
*** Bug 361892 has been marked as a duplicate of this bug. ***
