On Friday 2006 December 01 11:46, Martin Waitz wrote: > > That's no different from mine. > > Well, there simply is no proxy object inbetween. That's fine, I was only using the proxy object to allow additional information into the submodule object. Actually, I think it would always be better to use a proxy object otherwise you have an error in the tree object, because it will refer to an object that does not exist. The proxy object is allowed to refer to objects that don't exist because it's not a tree object. > > Is that commit in the submodule or the supermodule? > > Well, logically that commit belongs to the submodule and is referenced > by the tree in the supermodule. > Phyisically it is stored in the projects object database which is > shared between the supermodule and all submodules (at least in my > implementation). Hmmm, "shared"? It must still be in the submodule physically though, and presumably the supermodule uses alternatives to get access to it? Otherwise the submodule will be impossible to separate from the supermodule. > > I also want to know how we tell the difference between a > > commit-in-supermodule and a > > commit-in-supermodule-which-is-actually-in-submodule. > > There is no difference. Okay. I think I'm still a bit lost then. I suppose I'll wait for your patches to understand. Andy -- Dr Andy Parkins, M Eng (hons), MIEE andyparkins@xxxxxxxxx - 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