I think submodules are a good way to go. That would leave us with 3 repos as the core Apache NuttX. One for 'nuttx' which, is Greg suggests, should always be exclusively the OS. One for 'apps'. And one for "linking" them together, and for providing other NuttX infrastructure that may not be appropriate in the core OS repo.
And the purpose of the third repositories with two submodules is... what? We discussed this configuration before as a device to support automated testing which requires both both an operating system and test applications. Is that the intent here? That might be a good testing solution, but is probably premature to discuss here.
DavidS was referring to something else. I think a David was referring to a way to make releases from a single repo. I would think the first and most straightforward solution for that would be two synchronized releases from two separate repositories. Keeping the releases as loosely coupled as possible, I think, would provide the greatest flexibility to end-users. The loss of flexibility would have to be balanced against the level of effort. Would the purpose of such a third repository just for releases be an attempt to reduce effort?
What is the final form of the release? In the past it was two tagged repositories and two tarballs with the same versioning. What would be the form of the release in this case be?
