Re: git push recurse.submodules behavior changed in 2.13

From: John Shahid <jvshahid@gmail.com>
Date: Jun 16, 2017, 14:11 UTC
Message-ID: <CAE5=+KWOxNxsLGEV3FEf0i7WM20ttE_34D7qHiPAvRAWi+6JAg@mail.gmail.com>
In-Reply-To: <CAGZ79ka=icZDS-6q2dGSxyeLxYw+Zd1M_DSWzmhmHYtbTQTvZw@mail.gmail.com>

On Mon, Jun 12, 2017 at 1:27 PM, Stefan Beller <sbeller@google.com> wrote:

Show 9 quoted lines

> On Sat, Jun 10, 2017 at 6:28 AM, John Shahid <jvshahid@gmail.com> 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)

I was under the impression that Jonathan and may be others considered the fact that `git push --recurse-submodules=on-demand` doesn't work as before an unintentional change. He asked me previously if pushing without a refspec will work for us and I responded with a yes. The question remains if everyone is on board with change push without refspec to use `push.default` in the parent repo as well as submodules.

Cheers,

JS