Re: git worktrees must exist even if locked

On Thu, May 11, 2017 at 3:24 AM, taylor, david wrote: > The Git documentation in describing worktrees says that one reason > why you might want to lock a worktree is to prevent it from being pruned > if it is on a removable media that isn't currently mounted. > > So, my

Re: git worktrees must exist even if locked

On Tue, May 16, 2017 at 5:43 AM, Junio C Hamano wrote: > "taylor, david" 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

Re: git worktrees must exist even if locked

david >> Sent: Wednesday, May 10, 2017 4:25 PM >> To: git@vger.kernel.org >> Subject: git worktrees must exist even if locked >> >> The Git documentation in describing worktrees says that one reason >> why you might want to lock a worktree is to prevent it

RE: git worktrees must exist even if locked

not break the use of Git with worktrees that live elsewhere nor commands that don't require a repository. > -Original Message- > From: taylor, david > Sent: Wednesday, May 10, 2017 4:25 PM > To: git@vger.kernel.org > Subject: git worktrees must exist even if locked > >

git worktrees must exist even if locked

The Git documentation in describing worktrees says that one reason why you might want to lock a worktree is to prevent it from being pruned if it is on a removable media that isn't currently mounted. So, my expectation was that if the worktree is inaccessible (and locked), Git would pretend that