Correct. That's exactly what I was trying to articulate, an aggregated view that just reflects the status of submodules.
- Jason On Thu, Feb 8, 2018, at 4:15 AM, Bertrand Delacretaz wrote: > Hi, > > On Thu, Feb 8, 2018 at 1:37 AM, Jason E Bailey <j...@apache.org> wrote: > > ...In either case, you'd end up with a central location with a snapshot of > > the latest code that is individually managed in it's own repo.... > > IIUC this has no impact on the existing repositories, it's just an > additional one that uses submodules and Jenkins to keep that > aggregated snapshot mostly up to date? > > If yes I think that's interesting - I wouldn't want us to be too > dependent on submodules, but if it's a distinct aggregated view that > sounds useful. > > -Bertrand
