henri GEIST <henri.geist@xxxxxxxxxxxxxxxxx> writes: > I plan to use a config file containing lines like > > "path_to_poited_repo SHA1_of_intended_commit URL_of_origin" > > the URL part will not be required. > > this file will be a list of pointer to other project. I wasn't paying attention to this thread, but I have to ask "why" here. The first two are what gitlink was designed to do in the superproject that ties multiple submodules together, and the last one is also supplied by the .gitmodules in that superproject. This seems to be adding the same information in a redundant way by saying "this version A0 of submodule A wants version B0 of submodule B and version C0 of submodule C" when the supermodule can say "the consistent view I record is to have version A0, B0 and C0 of submodules A, B and C, respectively". I also suspect that allowing each submodule to know and demand specific versions of other submodules will lead to inconsistencies. Which version of submodule C would you demand to have when submodule A wants version C0 and submodule B wants version C1 of it? -- 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