On Fri, Jan 17, 2020 at 04:03:19PM -0500, Jeff King wrote: > (like trying to replace the use of "repo" in Android) Oops, you saw right through us ;) > It would make more sense to me to either (or both): > > - make sure that .gitmodules has enough information about which branch > to use for each submodule Hum. I don't work with them day to day, but aren't we already in that state? Is that not what the 'branch' option for each submodule means? > > - offer an extra option for the default branch to use for any > submodules. This is still not general enough to cover all situations > (e.g., the bar/baz you showed above), but it at least makes it > relatively easy to cover the simple cases, without breaking any > existing ones. Yeah, this is sort of the direction my mind went too - "not --branch recursively, but --submodule-branch". But that breaks down when you've got a nontrivial number of submodules, at which point you're gonna have a hard time unless you've got the .gitmodules configured correctly. Well, as for this patch, let me try it with just --single-branch and see whether that works for the case the user reported. I can head back to the drawing board if not. - Emily
