On Tue, May 16, 2017 at 5:43 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > "taylor, david" <David.Taylor@xxxxxxxx> 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