I didn't know that about git submodules. TIL. But yes, it seems it would make sense to update the submodule hashes to the latest stable whenever Gerrit merges something to that branch.
Of course, I may be way off base as to what purpose qt5.git is actually meant to serve, but from these pages: http://qt-project.org/wiki/Building_Qt_5_from_Git http://qt-project.org/wiki/Code_Reviews http://qt-project.org/wiki/Get_The_Source it seems to be the recommended approach for contributing fixes and features. If that's the case, then (imho) it would make most sense to have it track the same thing the build bot is building against. On Thu, Dec 5, 2013 at 9:45 PM, Nicolás Alvarez <[email protected]>wrote: > 2013/12/5 Chris Colbert <[email protected]>: > > In the broader sense, if the Gerrit only merges to 'stable' once the > build > > succeeds and (presumably) tests pass, what's the reasoning behind not > having > > qt5.git default the submodules to the 'stable' branch? > > Git doesn't support making a submodule that points at "the stable > branch". Submodules always point to specific commit hashes. Maybe your > question is why the submodules aren't updated to the latest stable > more frequently? > > -- > Nicolás >
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
