Re: What's cooking in git.git (Feb 2020, #05; Tue, 25)

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Feb 26, 2020, 06:54 UTC
Message-ID: <CAPig+cR3H2qvCddWuWPNex=K-x0FyzKehpbOiv7W-s_4EAW1bQ@mail.gmail.com>
In-Reply-To: <xmqqo8tml1lv.fsf@gitster-ct.c.googlers.com>

On Tue, Feb 25, 2020 at 5:54 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 9 quoted lines

> * es/worktree-avoid-duplication-fix (2020-02-24) 3 commits
>  (merged to 'next' on 2020-02-25 at 74c612837a)
> + worktree: don't allow "add" validation to be fooled by suffix matching
> + worktree: add utility to find worktree by pathname
> + worktree: improve find_worktree() documentation
>
> "git worktree add" used to get confused that the director to be
> used to add a new worktreey, when given as a relative path, is
> different from an existing one. This has been corrected.

It looks like you inserted some text between the "r" and "y" of "directory", resulting in "director" and "worktreey".

The description of the patch series could perhaps be a bit clearer. How about this instead?

    In rare cases "git worktree add <path>" could think that <path>
    was already a registered worktree even when it wasn't and refuse
    to add the new worktree. This has been corrected.