Hi-- I have a project with a number of sub-projects in it. I want each sub- project to have it's own git repo, but at the same time I want to keep them "together". GitHub doesn't really facilitate this kind of structure. So I also have a Rubyforge project for the master project, but Rubyforge only offers a single git repo per project, so having a git repo for each subproject won't work there. So I've been stuck, trying to figure out how to accomplish both ends. Tonight I struck upon and idea that I thought for sure would not work, but to my surprise it seems to work fine.
I initialized a git repo for each subproject, than moved up to the master directory and initialize a git repo there too. The repo at the top does not seem to mind the repos in the subdirectories and just ignores the .git directory. So it would seem I can keep the individual repos I want for the subprojects and at the same time keep a master of all of the sub-projects in single git repo. Like I said, I'm surprised this seems to work. Is it really true? Can I really do this without incident? Does anyone have any experience with this setup. And even if it's workable in practice, is it a wise idea from a management standpoint? Thanks. Trans. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" 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/github?hl=en -~----------~----~----~----~------~----~------~--~---
