Stefan Beller <sbel...@google.com> writes: > I do not think that is a better place as not every consumer of module_list > (and module_list_compute as the nested function) will need to use the > submodule caching API.
Ah, if that is the case, then OK. I was imagining that module-list may someday would return a list of "struct" instances each of which describes a submodule and has .name and .path fields, or something, instead of just being a "here is the path to the submodule, go look it up yourself" interface. But we are not there (at least not yet--and I am not saying we agreed that we would eventually want to go there) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
