Re: What's cooking in git.git (Jul 2021, #03; Tue, 13)

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Jul 14, 2021, 02:16 UTC
Message-ID: <CAPig+cQfsACHAQhCrXDs==18p1Ds8MtMRZDmSfso9HsO6dF-qg@mail.gmail.com>
In-Reply-To: <xmqqmtqpzosf.fsf@gitster.g>

On Tue, Jul 13, 2021 at 9:07 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 9 quoted lines

> * sm/worktree-add-lock (2021-07-12) 3 commits
>  - worktree: teach `add` to accept --reason <string> with --lock
>  - worktree: mark lock strings with `_()` for translation
>  - t2400: clean up '"add" worktree with lock' test
>
>  "git worktree add --lock" learned to record why the worktree is
>  locked with a custom message.
>
>  Ready?

I think this series is ready and gave my Reviewed-by: here[1]. One of the new tests contains an unnecessary but harmless `test -f`[2], but it's such a minor nit that I doubt it's worth demanding a re-roll.

[1]: https://lore.kernel.org/git/CAPig+cSVsJ9AtAMqtRQpyuosCDCGi+mu2C1PJUK49WTb5KvcWQ@mail.gmail.com/ [2]: https://lore.kernel.org/git/CAPig+cQVSUg1aqry_hMydJ=Uo=-VhOog6TUTpG=0on0LUcw8Dg@mail.gmail.com/