Re: What's cooking in git.git (Dec 2021, #02; Tue, 7)

From: Elijah Newren <newren@gmail.com>
Date: Dec 8, 2021, 18:05 UTC
Message-ID: <CABPp-BEd-CLaAJvLpcE=zSinz1up17zh+iUrG--4AXUe765BBA@mail.gmail.com>
In-Reply-To: <xmqq8rwv6e0a.fsf@gitster.g>

On Wed, Dec 8, 2021 at 1:28 AM Junio C Hamano <gitster@pobox.com> wrote:

>
> Needs an Ack or Reviewed-by.
>  - ns/tmp-objdir                                                12-06          #2

Provided: https://lore.kernel.org/git/CABPp-BEJbS=5i+d-Aa_fCH-WAjSOhX+nSZk5Q9Kb6RiizFg7ZQ@mail.gmail.com/

> Will merge to 'next'?
>  - ld/sparse-diff-blame                                         12-06          #8

I'm in favor.

>  - js/scalar                                                    12-04         #15

Yes, please. I think everyone agrees there are additional things wanted, but the current patch series is good (and is already on the longer side), and it was always designed as the initial submission with 4-5 additional series coming. Those additional things can come in one of the future series.

>  - en/name-rev-shorter-output                                   12-04          #1

Dscho spoke up in favor of merging down (https://lore.kernel.org/git/nycvar.QRO.7.76.6.2112081237310.90@tvgsbejvaqbjf.bet/), and you did too 3 weeks ago when you commented,

""" In any case, this seems to give us a much better results than the current code, so let's take it and leave further futzing outside the scope. """ (from https://lore.kernel.org/git/xmqq35nv416j.fsf@gitster.g/)

I haven't changed the code since this comment of yours, just added some additional pointers in the commit message for future readers who want to tackle that "further futzing". :-)