I have a project where most branches have one subdirectory for the core program and other subdirectories for support scripts, programs and libraries. The supporting subdirectories vary from branch to branch. However, some branches contain just the core program, with no subdirectories. Starting from scratch, I would say the core program should be a submodule, but historically it was not populated as one. Is there a way to easily create such a pseudo-submodule branch in git, or are real submodules strongly preferred for this kind of scenario? (The added twist: I ran into this while importing a Subversion repository. git-svn identified two trees of history in the repository -- one history containing the core plus support trees, one history containing just the core program. Since the trees do have the same contents, only the commits are duplicated, but that is not quite ideal. It seems like using the current submodule code would mean that this kind of import would need two passes over the foreign repository, rather than one if the branch could be created after the parent tree is initially imported. I can live with that -- it is a rather unusual case -- but maybe there is a better way.) Michael Poole - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
