On Tue, Dec 05, 2006 at 10:01:25AM +0100, Uwe Kleine-Koenig wrote: > Hello, > > Andreas Ericsson wrote: > > The only problem I'm seeing atm is that the supermodule somehow has to > > mark whatever commits it's using from the submodule inside the submodule > > repo so that they effectively become un-prunable, otherwise the > > supermodule may some day find itself with a history that it can't restore. > One could circumvent that by creating a separate repo for the submodule > at checkout time and pull the needed objects in the supermodule's odb > when commiting the supermodule. This way prune in the submodule cannot > do any harm, because in it's odb are no objects that are important for > the supermodule. I _think_ Linus argued against doing this (for scalability reasons), although he didn't actually answer my question when I asked him directly. In his proposal you wouldn't need to do this, because the particular checked-out copy of the submodule that is located in a subdirectory of a superproject would not be allowed to be pruned and it seems that Martin has also implemented it like this. skimo - 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