On 7/11/2012 12:15, Peter Ansell wrote:
To extract the full history for the spin-api folder to a new repository you can use this guide that I have used successfully before [1]. Once you have extracted the tree to a new repository you can put it back into the original git repository as a submodule [2], which works roughly the same way as svn externals work if you are familiar with those. Cheers, Peter [1] https://help.github.com/articles/splitting-a-subpath-out-into-a-new-repo [2] http://git-scm.com/book/en/Git-Tools-Submodules
This is interesting. While I haven't spoken to my co-workers yet my gut feeling is that such a solution (of having the public repository a sub-module of TopBraid Suite code) is not "politically" feasible. I believe a good first step would be a solution in which I copy over changes back and forth between two otherwise independent repositories. Does either one of you have experience with that? How would I need to set this up to map a sub-folder of TopBraid-Suite with the top-level folder of SPIN-API?
Thanks Holger -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN. 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/topbraid-users?hl=en
