Re: Add an option to automatically submodule update on checkout

"Randall S. Becker" [off-list ref] writes:

I have to admit that I just assumed it would have to work that way
this would not be particularly useful. However, in thinking about
it, we might want to limit the depth of how far -b <name> takes
effect. If the super module brings in submodules entirely within
control of the development group, having -b <name> apply down to
leaf submodules makes sense (in some policies). However, if some
submodules span out to, say, gnulib, that might not make
particular sense.

I do not see a strong reason to avoid your own branches in "other
people's project" like this.

The submodule's upstream may be a project you have no control over,
but the repository you have locally is under your total control and
you can use any branch names to suit the need of your project as the
whole (i.e. the superproject and submodules bound to it).

The fact that local branch names are under your control and for your
own use is true even when you are not using submodules, by the way.