On Tuesday 12 June 2007, Lars Hjemli wrote: > On 6/12/07, Johannes Sixt <J.Sixt@xxxxxxxxxxxxx> wrote: > > > > KDE (superproject) > > > > +- kdelibs (subproject) > > > > | +- admin (subproject) > > > > | +- subdir1 > > > > | +- ... > > > > +- kdebase (subproject) > > > > | +- admin (subproject) > > > > | +- subdir2 > > > > | +- ... > > > > +- kdenetwork (subproject) > > > > | +- admin (subproject) > > > > | +- subdir3 > > > > | +- ... > > > > ... > > In this case, I would assume that e.g. kdelibs contain a submodule > entry for path admin in its index, accompanied by a .gitmodules file > saying that the path admin is mapped to this or that submodule. Exactly. That's just the "submodule" in "submodule" case we should support, too. > I > would not expect the KDE 'supersuperproject' to know about admin at > all, neither in its index nor .gitmodules. The admin submodule contains KDE specific things. So of course it also would be a submodule in the grand whole KDE superduper module. But that does not really matter. However, to not have a lot of copies of the admin submodule in .git/submodule/admin .git/submodule/kdelibs/.git/submodule/admin .git/submodule/kdebase/.git/submodule/admin .git/submodule/kdenetwork/.git/submodule/admin the just suggested submodule.<name>.repopath to specify a repository outside of .git/submodule to be shared by kdelibs,kdebase,... would be fine. Josef - 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
