Simplified version:

I have some a new convention operation in my rhino-tools repository on
GitHub. I want to move it to the rhino-etl repository. What's the
right/best way to do that? Does git help me? Do I do it the
old-fashioned manual way (i.e. copy/paste the CS file to my local
rhino-etl repository and add it there)? Something else?

Bonus round: How do you do this on an on-going basis as changes
continue to show up in the SF SVN repository and you want them in the
new project-specific repositories?


--Stuart

On Wed, Sep 9, 2009 at 4:14 PM, Stuart Laughlin <[email protected]> wrote:
> This is interesting. Currently Lee has a rhino-tools repository on
> GitHub which is a mirror of the SourceForge SVN repository. Ayende and
> I both forked it. I fixed a doc bug / typo and implemented a couple
> new convention operations in RhinoETL. Then Ayende broke the projects
> into separate repsositories. And others have forked those
> project-specific repositories.
>
> So, there is new development in the following places:
>
>  * SF SVN repository
>  * Lee's Rhino-Tools repository on GitHub and its descendents
>  * Ayende's project-specific repositories on GitHub and their descendants
>
> Merging from a descendant to a parent and vice-versa is pretty
> straight-forward, I reckon. And so is merging from SF SVN to
> rhino-tools on GitHub, I suppose (since in both cases there is a
> common ancestor). But how are changes to the SF SVN repository and the
> GitHub rhino-tools repositories merged to the project-specific
> repositories (and vice versa)? Is it equally straight-forward, even
> though these repositories technically do not share a common ancestor?
>
>
> --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
-~----------~----~----~----~------~----~------~--~---

Reply via email to