Some context. I simply want a container repository of a family of test projects that each are repositories in their own right. Just little executables that allow me to flesh out various ideas. My head is spinning now because subtree looks like overkill - and commits seem really complicated. I thought submodules was perfect but that approach seems to require the original repository to remain at github. I want to blow away all these little separate repositories and pull them under a single umbrella container repository while each can maintain it's trackability. Make sense?
Could someone please sketch how to do this? Thanks a million! Cheers, Doug On Oct 10, 9:03 pm, Tekkub <[email protected]> wrote: > I think you're looking for subtree merge:http://help.github.com/subtree-merge/ > Tekkub > GitHub Tech Support > http://support.github.com/ > Join us on IRC: #github on freenode.net > Discussion group: [email protected] > > On Fri, Oct 9, 2009 at 2:56 PM, Dugla <[email protected]> wrote: > > > I'm doing a bit of housecleaning and I would like to move previously > > separate repositories into a parent repository. Yes, I can download > > tarballs of each project and then install them under a parent > > directory and push back up to github, but won't I then loose all my > > commit messages once the parent becomes the repository? > > > Thanks in advance, > > Doug > > @dugla --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
