Re: git push recurse.submodules behavior changed in 2.13

On Sat, Jun 10, 2017 at 6:28 AM, John Shahid [off-list ref] wrote:

bump. it's been a while and I'm still not clear what the next steps
are. I'm happy to send a patch but I would like to get a consensus
first.

What do you want a consensus on?
(Is the change in 2.13 a bug or feature? I considered it enough
of a feature to not pursue an urgent bug fix. Maybe I misunderstood
the discussion)

This thread has diverged into lots of things that could be done. Jonathan
pointed out 3 possible ways forward. (1) and (3) are being worked on,
(2) is a new thing that nobody (not Brandon nor me) have on our radar
for what to work on next.  So maybe that is a good idea to get started
when you want to get into sending a patch?

Also I have the impression that there may be one corner case, in which
the handling of refspecs is missed, i.e. maybe we'd need a list (in the
man page eventually) on what currently happens when recursing in
combination with remote/refspecs or other options.