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

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Dec 22, 2020, 20:25 UTC
Message-ID: <CAPig+cT7q76NMubK3N2R-OmRUnH6HVWOt7eKRNCVjtv_qWK97g@mail.gmail.com>
In-Reply-To: <xmqqo8ilhafa.fsf@gitster.c.googlers.com>

On Tue, Dec 22, 2020 at 3:08 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 7 quoted lines

> * es/worktree-repair-both-moved (2020-12-21) 1 commit
>  - worktree: teach `repair` to fix multi-directional breakage
>
>  "git worktree repair" learned to take advantage of the fact that it
>  knows both ends (i.e. the main repository is found in the location
>  the command runs, the worktrees are given as arguments) to deal
>  with the case where both the repository and the worktree moved.

The lengthy parenthetical comment makes this description a bit difficult to digest. I had to read it a couple times to understand what it was saying. Perhaps it could be simplified, perhaps like this:

    "git worktree repair" learned to handle the case when both the
    repository and worktrees have been moved.

By the way, an unrelated patch[1] I sent a day before sending the es/worktree-repair-both-moved topic doesn't seem to have made it into 'seen', so I'm wondering if it was overlooked (or perhaps it just hasn't been processed yet).

[1]: https://lore.kernel.org/git/20201220212740.44273-1-sunshine@sunshineco.com/