Re: [PATCH 4/6] worktree: the "locked" mechanism is already implemented
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Jul 19, 2015, 03:06 UTC
- Message-ID
- <CAPig+cRSWWnWyV2HJVjS9MkAxv_gLk=KauSbNvw_3k2N_rkuVg@mail.gmail.com>
- In-Reply-To
- <afdc2580349017ae26aade63c9e5ea2b4a986beb.1437271363.git.mhagger@alum.mit.edu>
On Sat, Jul 18, 2015 at 10:10 PM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
Show 17 quoted lines
> So remove it from the "BUGS" section. > > Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu> > --- > Documentation/git-worktree.txt | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/Documentation/git-worktree.txt b/Documentation/git-worktree.txt > index 6cb3877..d5aeda0 100644 > --- a/Documentation/git-worktree.txt > +++ b/Documentation/git-worktree.txt > @@ -167,8 +167,6 @@ performed manually, such as: > warn if the worktree is dirty) > - `mv` to move or rename a worktree and update its administrative files > - `list` to list linked working trees > -- `locked` to prevent automatic pruning of administrative files (for instance, > - for a worktree on a portable device)
This patch should be dropped. This BUGS item is not referring to the low-level implementation of locking, but rather to the proposed user interface command ("git worktree lock") for manipulating the 'locked' file so that the user doesn't need detailed knowledge about the underlying implementation.