git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git worktrees must exist even if locked

From
Duy Nguyen <pclouds@gmail.com>
Date
May 29, 2017, 10:17 UTC
Message-ID
<CACsJy8A691aGfKfa7h1y7A3sgnWgDm_eLA5tj78ES1XjP+mK5Q@mail.gmail.com>
In-Reply-To
<xmqqshk568s4.fsf@gitster.mtv.corp.google.com>
On Tue, May 16, 2017 at 5:43 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 10 quoted lines
> "taylor, david" <David.Taylor@dell.com> writes:
>
>> The original report was against Git v2.12.2.  I have since tried v2.12.3, v2.13.0,
>> and the next branch.  All exhibit the same symptoms.
>>
>> Even if you ignore the original scenario for creating the problem, if I do a 'rm -rf' or 'mv'
>> of a tree that contains within it worktrees, that should not break the use of Git with
>> worktrees that live elsewhere nor commands that don't require a repository.
>
> Duy, any ideas?

We are supposed to tolerate missing worktrees if locked. I'm guessing that lots of changes in get_worktrees() lately may perhaps forget about this and be too strict on locked worktrees.

-- 
Duy
Previous: Junio C Hamano
Message 3 of 3 in “RE: git worktrees must exist even if locked”
  1. taylor, davidMay 15, 2017
  2. Junio C HamanoMay 15, 2017
  3. Duy NguyenMay 29, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.