Re: Slow pushes on 'pu' - even when up-to-date..

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 3, 2016, 22:06 UTC
Message-ID: <xmqqd1jh5bq2.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CAGZ79kY6FpTD1VJQ=+wJ0FrXe9LjJ=NBwLsOku0R4FerAmQGJQ@mail.gmail.com>

Stefan Beller <sbeller@google.com> writes:

Show 16 quoted lines

> On Mon, Oct 3, 2016 at 2:17 PM, Stefan Beller <sbeller@google.com> wrote:
>>
>> * sb/push-make-submodule-check-the-default (2016-08-24) 1 commit
>>  - push: change submodule default to check
>>
>>  Turn the default of "push.recurseSubmodules" to "check".
>>
>>     Will hold to wait for hv/submodule-not-yet-pushed-fix
>>
>>     This reveals that the "check" mode is too inefficient to use in
>>     real projects, even in ones as small as git itself.
>>     cf. <xmqqh9aaot49.fsf@gitster.mtv.corp.google.com>
>
> So maybe we should eject this series from pu as long as
> hv/submodule-not-yet-pushed-fix is ejected to enable you
> running pu happily.

I am planning to merge lt/abbrev-auto to 'next' together with Peff's ambiguous-short-object-names series in today's pushout.

Just FYI, there is another integration branch called 'jch' that typically has several topics more than 'next' but does not merge things I haven't looked at (or things I have looked at and decided not ready). That is what I use for my daily work. You can grab it out of "git log --oneline --first-parent master..pu", or from my broken-out repository (git://github.com/gitster/git/).