I've read so much on rebase vs merge vs grafting vs subtrees vs stitching and so on that I'm more confused now than when I started. :)
I give up on conjoining the historical repos, let alone current. The idea of being able to seamlessly follow a feature's changes from now back to the earliest incarnation in a single repo is charming, but not worth the work it's taking me to figure out how. And really, how often if ever is somebody going to do that? I may not have reached the intended target, but the effort it is not wasted. We now have all of Leo's public code in a single toolset and single host (GitHub). The archaeological record is now more resilient to old host services like Sourceforge & Tigris CVS being turned off. cheers, -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
