Re: pd/fetch-jobs, was Re: What's cooking in git.git (Sep 2019, #01; Sat, 7)

From: Palmer Dabbelt <palmer@sifive.com>
Date: Sep 16, 2019, 20:40 UTC
Message-ID: <mhng-98edf120-10e7-4944-bfee-fd984047a6b6@palmer-si-x1c4>
In-Reply-To: <xmqqh85cb0hr.fsf@gitster-ct.c.googlers.com>

On Mon, 16 Sep 2019 10:43:28 PDT (-0700), gitster@pobox.com wrote:

Show 15 quoted lines

> Palmer Dabbelt <palmer@sifive.com> writes:
>
>> ...  It looks
>> like there are some test failures when I rebase to the latest master,
>> which I'm happy to fix.  Just let me know if I should:
>
>> * Send just the first 4 patches, holding onto the last one for later.
>> ...
>> * Send just a single patch, which wouldn't add the --fetch-jobs and
>> --submodule-fetch-jobs arguments.
>
> It is either one of these two, I would say.  I am personally much
> more comfotable with the usual "backward incompatibility migration"
> form (i.e. the former), but apparently I am nto the only person on
> the list so ... ;-)

OK, well, just dropping the last patch causes the tests to pass when rebased on master, so I'll send that out as it's easier for me. Is there a policy for deprecation timelines?