On Tue, Jun 17, 2014 at 1:26 PM, Julian Gonggrijp
Andrey Semashev wrote:
There is a way to associate it with the commit - if the cache is stored in the superproject and generated when the superproject is updated to refer to the new commit in the submodule. The updated metadata can be committed in the same commit as the reference update.
I think this might be the best idea. It would be reasonably simple to implement and it covers most cases. Only if maintainers want to do custom checkouts on somebody else's module they'll have to use the "blind" fallback, but I guess that's acceptable.
Note that this would still require hooks, but only for the superproject maintainers.
I'm not sure how the superproject is currently updated but I suspect it might be through polling and not hooks. I hope someone more informed can comment on this.