Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <xmqqr1kwk0h9.fsf@gitster.c.googlers.com>
In-Reply-To: <xmqqr1kwk0h9.fsf@gitster.c.googlers.com>
From:   Eric Sunshine <sunshine@sunshineco.com>
Date:   Wed, 3 Mar 2021 22:41:49 -0500
Message-ID: <CAPig+cRqED-d_hFN80UuPhS+77k6qw_G9Q-m9tWUZsNynQfVvA@mail.gmail.com>
Subject: Re: [ANNOUNCE] Git v2.31.0-rc1
To:     Junio C Hamano <gitster@pobox.com>
Cc:     Git List <git@vger.kernel.org>,
        Linux Kernel <linux-kernel@vger.kernel.org>,
        git-packagers@googlegroups.com
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, Mar 3, 2021 at 7:23 PM Junio C Hamano <gitster@pobox.com> wrote:
> Eric Sunshine (3):
>       worktree: teach `repair` to fix multi-directional breakage

The merge message associated with this change is:

    "git worktree repair" learned to deal with the case where both the
    repository and the worktree moved.

which seems worth mentioning in the v2.31.0 release notes, so it's a
bit surprising that it is not mentioned anywhere. I haven't
investigated how the release notes are generated from the merge
messages, so it is unclear if this is a mere oversight, an intentional
omission, or a tooling error.