Hi! On Fri, Feb 15, 2013 at 11:01:54AM +0000, Daniel Willmann wrote: > Hello, > > everything was migrated to git and should be working now. If you have > problems, speak now.
That`s awesome, nice job Daniel and others. > > The new web frontend is here: > https://git.enlightenment.org/core/efl.git/ > Phabricator: > https://phab.enlightenment.org/ > > Mailinglist for commits: > https://lists.sourceforge.net/lists/listinfo/enlightenment-git > > Read-only git access: > git clone git://git.enlightenment.org/core/efl.git > > Read/write for developers: > git clone ssh://[email protected]/core/efl.git > Have we already decided about our workflow with git? Are we going to have an integrator or so? Are we - developers - going to have a hosting space so we can maintain our forks and ask pull requests from? > > If you have uncommitted changes in your svn or git-svn checkout: > > Here is how you could do it depending on whether you have pure svn or > git-svn: > > SVN > --- > * Update SVN so you are at the current revision: > $ svn up > $ svn info trunk/efl/ |grep Revision > -> Should be revision 83942 > > * Clone the new repo with git clone > > * Find the matching commit in git > $ git log --grep "SVN revision: 83942" > -> This will show you commit c5a8a6b5 > > * Reset your working directory to this commit (in a new branch) > $ git checkout -b svn-import c5a8a6b5 > > * Copy your files over from SVN. You can just copy everything (do omit > the .svn directories, though) as the repositories will be in the same > state now. > > * Check that the changes make sense - git diff should now provide the > same output as svn diff > > * Save the changes temporarily > $ git stash > > * Checkout master > $ git checkout master > > * Apply the changes again > $ git stash pop > > * After you're done committing delete the branch > $ git branch -D svn-import > > git-svn > ------- > * Export all your commits that are not upstream yet > $ git format-patch git-svn..HEAD > -> Creates numbered patch files > > * Clone the new repository with git clone somewhere > > * Apply the patches to the new repository > $ git am 00*.patch > > * For the last command - depending on your checkout - you will probably > need to add the option -p to adjust the location of the patches. > So if you did a checkout of the complete trunk/ you'll need to pass > (I think) -p2 to git am. > > If you have any problems or patches don't apply cleanly, feel free to ask. > > > Regards, > Daniel > > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Leandro Dorileo ProFUSION embedded systems http://profusion.mobi ------------------------------------------------------------------------------ The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
