From: Eric Sunshine <sunshine@sunshineco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Feb 2020, #05; Tue, 25)
Date: Wed, 26 Feb 2020 01:54:01 -0500 [thread overview]
Message-ID: <CAPig+cR3H2qvCddWuWPNex=K-x0FyzKehpbOiv7W-s_4EAW1bQ@mail.gmail.com> (raw)
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:
> * 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.
next prev parent reply other threads:[~2020-02-26 6:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 22:54 What's cooking in git.git (Feb 2020, #05; Tue, 25) Junio C Hamano
2020-02-26 6:54 ` Eric Sunshine [this message]
2020-02-26 16:29 ` Junio C Hamano
2020-02-26 10:38 ` Alban Gruin
2020-02-26 16:33 ` Junio C Hamano
2020-02-26 20:39 ` Martin Ågren
2020-02-26 20:54 ` Martin Ågren
2020-02-26 21:06 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPig+cR3H2qvCddWuWPNex=K-x0FyzKehpbOiv7W-s_4EAW1bQ@mail.gmail.com' \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).