http://progit.org/book/ch5-3.html
git-format-patch is the preferred command, I think. So generate patches for your changes, and apply them to your new repo. 2009/9/10 Stuart Laughlin <[email protected]> > > On Wed, Sep 9, 2009 at 6:05 PM, Ayende Rahien<[email protected]> wrote: > > > > Not sure that I am following what you mean. > > > > I'm saying that when we get rid of the SF SVN repository, we should > also get rid of these: > > http://github.com/leemhenson/rhino-tools/network/members > > Right? > > And so then I'm thinking about how I am going to get the changes that > I made in my obsolete rhino-tools git repository > (http://github.com/sclaughl/rhino-tools/tree/master) over to the new > project-specific repository > (http://github.com/sclaughl/rhino-dsl/tree/master). > > Likewise and finally, if there are any commits made to SF SVN repo (or > the monolithic rhino-tools repo) on GitHub since the projects were > broken out on GitHub, these commits will need to be moved to the new > project-specific repos as well. > > Am I making sense now? I'm just wondering how this can be handled in git > world. > > > --Stuart > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
