Re: What's cooking in git.git (Jan 2020, #04; Wed, 22)

From: Elijah Newren <newren@gmail.com>
Date: Jan 22, 2020, 22:37 UTC
Message-ID: <CABPp-BHMwkP5r2tmVfmrjVM904EnhEAQ8hqCbxQ7QEg+vyRNZQ@mail.gmail.com>
In-Reply-To: <xmqqr1zr5e5e.fsf@gitster-ct.c.googlers.com>

On Wed, Jan 22, 2020 at 2:19 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 12 quoted lines

> --------------------------------------------------
> [New Topics]
>
> * en/simplify-check-updates-in-unpack-trees (2020-01-07) 1 commit
>   (merged to 'next' on 2020-01-15 at 586c055b69)
>  + unpack-trees: exit check_updates() early if updates are not wanted
>
>  Originally merged to 'next' on 2020-01-09
>
>  Code simplification.
>
>  Will merge to 'master'.

This is v2 of the series; and it looks good.  But...

Show 6 quoted lines

> * en/unpack-trees-check-updates-simplify (2020-01-04) 1 commit
>  - unpack-trees: exit check_updates() early if updates are not wanted
>
>  Code simplification.
>
>  Will merge to 'next'.

...this is v1 of the same submission. We don't need both v1 and v2 of the same patch to be merged (the only difference between the two is that v2 has a more detailed commit message); luckily, the one you already merged to next is v2. Can you just drop the en/unpack-trees-check-updates-simplify topic?