On Sun, May 20, 2007 at 11:33:17AM -0700, Junio C Hamano wrote: > Jan Hudec <bulb@xxxxxx> writes: > > - If you fetch from more than one location, you want to fetch subproject > > from location corresponding to where you fetch superproject from. > > Not at all. There is no reason to believe that the case that > superproject and subproject come from related URLs is more > common. One of the reasons to do a separated project > organization is to allow looser bindings of the project from > project administrative viewpoint. The integrator may not > necessarily have any control over what the subproject guys do, > and more importantly, the subproject people do not even care nor > be aware of the fact that their project is sometimes bound > inside other peoples' superprojects. Think of the embedded > appliance vendor binding the kernel, libc and busybox in their > superproject that holds them together with the build > infrastructure. The kernel folks certainly do not particularly > care about the vendor. I think what Jan means is that if there are two (or more) copies of the superproject then it is more likely that the subproject commit can be found in the subproject repo "pointed to" (e.g., through my submodule.*.url) by the superproject repo you fetched from. 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
