From: Eric Sunshine <sunshine@sunshineco.com>
Date: Mon, 08 Jun 2020 15:19:48 GMT
Subject: Re: [PATCH 8/8] worktree: make "move" refuse to move atop missing registered worktree
Message-ID: <CAPig+cSzam0fTBrs=3MP6jieD4DBNCgx9kkrBm1+ahhmPWtrjA@mail.gmail.com>
In-Reply-To: <20200608062356.40264-9-sunshine@sunshineco.com>

On Mon, Jun 8, 2020 at 2:25 AM Eric Sunshine <sunshine@sunshineco.com> wrote:
> "git worktree add" takes special care to avoid creating a new worktree
> at a location already registered to an existing worktree even if that
> worktree is missing (which can happen, for instance, if the worktree
> resides on removable media). "git worktree move", however, is not so
> careful when validating the destination location and will happily move
> the source worktree atop the location of a missing worktree. This leads
> to the anomalous situation of multiple worktrees being associated with
> the same path, which is expressively forbidden by design. For example:

s/expressively/expressly/