Yeah, I've already went thru these. But I want (much) more details. I can ask a bunch of random questions on this list, like: * Why after 'submodule update' it becomes detached, what if I want it to stay on certain branch? * How do I control which branches are fetched? * What if I do 'commit -a' standing in /super, will /super/submodule commit as well? * What if I'm standing in /super/submodule and do 'commit -a'? Will super notice it in any way? But I was hoping that it's all summarized somewhere already. - Dmitry On 8/7/07, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > Hi, > > On Tue, 7 Aug 2007, Dmitry Kakurin wrote: > > > Where can I find more information about submodules? > > I'm interested in both internal implementation details and how to use them. > > Most information is found in git-submodule.sh, although > Documentation/git-submodule.txt has beginnings of a good documentation. > > The basic idea is this: > > A subdirectory contains a self-contained project. > > Once that project is at a stage you want to have in the superproject, you > can commit that submodule state, much like a subdirectory. > > However, the history can progress in much coarser steps for the > superproject. IOW an ideal case for msysgit.git, where we want to have a > stable version which can be checked out with GitMe. > > Also, find more about submodules here: > > http://git.or.cz/gitwiki/SubprojectSupport?highlight=%28submodule%29 > > Ciao, > Dscho - 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
