Using a Git submodule as a container of other Git submodules in GDevCon1_CML-DQMH example

[DowNow_]

This repo uses nested submodules, GDevCon1_CML-DQMH at https://github.com/DelacorLLC/GDevCon1_CML-DQMH. The "Libraries" Git submodule contains six Git submodules and no other code. This hierarchy works for me, but can anyone explain the benefits of using this technique? I'm getting some team resistance.

I think of Libraries as a reusable collection of packages. Maintenance is easier, neater. Libraries is cohesive and decoupled. Please post any rationale, use case, or comment for using a Git submodule collection of other submodule. Thanks, cc

[Darren]

I'll let someone else post about the benefits of using submodules. I happen to think they're more trouble than they're worth, and my preference is just to have separate non-nested repos for individual software components.