Daniel Barkalow wrote:
There are a bunch of use cases which people see as subprojects, with slightly different desires. For example, I personally don't think there's any point to subprojects if a commit of the parent project doesn't specify the embedded commits of each subproject (so, for example, you can use bisect on the parent project to figure out which act of updating a subproject broke the resulting system). AFAICT, your design doesn't handle that, but uses the most recently fetched versions of all subprojects, with the revision control of the parent only handling revisions in the arrangement and membership of subprojects in the parent.
That isn't that much different than what I outlined. Instead of recording the branch name and directory in the parent project, you could record the commit SHA1 ID for each subproject and directory. The machinery changes but the idea is the same.
- 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