For those possibly not watching SourceForge, Oren moved all of the files. This clears any confusion over which repository to use.
On Thu, Sep 10, 2009 at 7:57 AM, Paul Cowan <[email protected]> wrote: > Thanks for the update. > > 2009/9/10 Ayende Rahien <[email protected]> > > Paul, There will be an official announcement, but basically, it just >> means that some projects got forcibly moved from SVN to Git. >> The official mirror is the one on my account >> >> On Thu, Sep 10, 2009 at 1:06 PM, Paul Cowan <[email protected]> wrote: >> >>> Hi, >>> >>> I am a horn developer. Are you guys going to destroy the svn repo >>> anytime soon? >>> >>> I know Rhino is a very well run project so I guess there will be some >>> sort of public announcement of some sort as to the new lay of the land. >>> >>> Am I reading this correctly in that there is no central repo? >>> >>> Will you be using an svn mirror? >>> >>> >>> 2009/9/10 Lee Henson <[email protected]> >>> >>>> 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 >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Cheers >>>> >>>> Paul Cowan >>>> >>>> Cutting-Edge Solutions (Scotland) >>>> >>>> http://thesoftwaresimpleton.blogspot.com/ >>>> >>>> >>>> >>>> >> >> >> -- >> Cheers >> >> Paul Cowan >> >> Cutting-Edge Solutions (Scotland) >> >> http://thesoftwaresimpleton.blogspot.com/ >> >> >> >> >> -- Tim Barcz Microsoft ASPInsider http://timbarcz.devlicio.us http://www.twitter.com/timbarcz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
