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

[PATCH 4/6] worktree: the "locked" mechanism is already implemented

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Jul 19, 2015, 02:10 UTC
Message-ID
<afdc2580349017ae26aade63c9e5ea2b4a986beb.1437271363.git.mhagger@alum.mit.edu>
In-Reply-To
<cover.1437271363.git.mhagger@alum.mit.edu>
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)
 
 GIT
 ---

-- 
2.1.4
Previous: Eric SunshineNext: Eric Sunshine
Message 8 of 14 in “Various tweaks to 'worktree'-related manpages”
  1. 0/6 Various tweaks to 'worktree'-related manpagesMichael Haggerty, Jul 19, 2015
  2. 1/6 worktree: consistently use term "linked working tree" in manpagesMichael Haggerty, Jul 19, 2015
  3. Eric SunshineJul 19, 2015
  4. 2/6 worktree: remove references to "git checkout --to" from the manpageMichael Haggerty, Jul 19, 2015
  5. Eric SunshineJul 19, 2015
  6. 3/6 worktree: fix incorrect references to file "locked"Michael Haggerty, Jul 19, 2015
  7. Eric SunshineJul 19, 2015
  8. 4/6 worktree: the "locked" mechanism is already implementedMichael Haggerty, Jul 19, 2015
  9. Eric SunshineJul 19, 2015
  10. 5/6 config.txt: refer to "git worktree prune", not "prune --worktree"Michael Haggerty, Jul 19, 2015
  11. Eric SunshineJul 19, 2015
  12. 6/6 worktree: wordsmith worktree-related manpagesMichael Haggerty, Jul 19, 2015
  13. Eric SunshineJul 19, 2015
  14. Eric SunshineJul 19, 2015

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.