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

[PATCH v2 3/5] Documentation/config: fix stale "git prune --worktree" reference

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Jul 20, 2015, 05:29 UTC
Message-ID
<1437370162-8031-4-git-send-email-sunshine@sunshineco.com>
In-Reply-To
<1437370162-8031-1-git-send-email-sunshine@sunshineco.com>
From: Michael Haggerty <mhagger@alum.mit.edu>

This should have been changed to "git worktree prune" by df0b6cf (worktree: new place for "git prune --worktrees", 2015-06-29)

[es: reword commit message]
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
---
 Documentation/config.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 3e37b93..7f65dbb 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -1293,7 +1293,7 @@ gc.pruneExpire::
 
 gc.pruneWorktreesExpire::
 	When 'git gc' is run, it will call
-	'prune --worktrees --expire 3.months.ago'.
+	'git worktree prune --expire 3.months.ago'.
 	Override the grace period with this config variable. The value
 	"now" may be used to disable the grace period and prune
 	$GIT_DIR/worktrees immediately.
-- 
2.5.0.rc2.386.g87d813d
Previous: Eric SunshineNext: Eric Sunshine
Message 4 of 9 in “mh: worktree-related doc fixes”
  1. 0/5 mh: worktree-related doc fixesEric Sunshine, Jul 20, 2015
  2. 1/5 Documentation/git-worktree: consistently use term "linked working tree"Eric Sunshine, Jul 20, 2015
  3. 2/5 Documentation/git-worktree: fix incorrect reference to file "locked"Eric Sunshine, Jul 20, 2015
  4. 3/5 Documentation/config: fix stale "git prune --worktree" referenceEric Sunshine, Jul 20, 2015
  5. 4/5 Documentation/git-worktree: wordsmith worktree-related manpagesEric Sunshine, Jul 20, 2015
  6. 5/5 config: rename "gc.pruneWorktreesExpire" to "gc.worktreePruneExpire"Eric Sunshine, Jul 20, 2015
  7. Michael HaggertyJul 20, 2015
  8. Eric SunshineJul 24, 2015
  9. Junio C HamanoJul 24, 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.