On Thu, 12 Apr 2007, Sam Vilain wrote:I assume you mean "you might want to keep all of the subprojects' objects in the same git object directory". And yes, that's absolutely true, but it's technically no different from just using GIT_OBJECT_DIRECTORY to share objects between totally unrelated projects, or using git/alternates to share objects between (probably *less* unrelated repositories, but still clearly individual repos). So the main point of superproject/subprojects is to allow independence (because independence is what allows it to scale), but there is nothing to say that things *have* to kept totally isolated. Linus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Stephen Rothwell | Re: Announce: Linux-next (Or Andrew's dream :-)) |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Arjan van de Ven | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 33/37] dccp: Initialisation framework for feature negotiation |
| Christoph Lameter | Network latency regressions from 2.6.22 to 2.6.29 |
