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

[PATCH 4/4] checkout branch: prime cache-tree fully

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 20, 2009, 10:58 UTC
Message-ID
<1240225100-29960-5-git-send-email-gitster@pobox.com>
In-Reply-To
<1240225100-29960-4-git-send-email-gitster@pobox.com>

When switching to another branch, the earlier code relied on incremental invalidation of cache-tree entries to degrade it. While it is not wrong per-se, we know that the resulting index must fully match the branch we are switching to unless the -m (merge) option is used.

We should simply fully re-prime the cache-tree using the new tree object in such a case. And for safety, invalidate the cache-tree as a whole in other cases.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 builtin-checkout.c |    9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/builtin-checkout.c b/builtin-checkout.c
index ffdb33a..efa1ebf 100644
--- a/builtin-checkout.c
+++ b/builtin-checkout.c
@@ -368,14 +368,17 @@ static int merge_working_tree(struct checkout_opts *opts,
 	int ret;
 	struct lock_file *lock_file = xcalloc(1, sizeof(struct lock_file));
 	int newfd = hold_locked_index(lock_file, 1);
+	int reprime_cache_tree = 0;
 
 	if (read_cache() < 0)
 		return error("corrupt index file");
 
+	cache_tree_free(&active_cache_tree);
 	if (opts->force) {
 		ret = reset_tree(new->commit->tree, opts, 1);
 		if (ret)
 			return ret;
+		reprime_cache_tree = 1;
 	} else {
 		struct tree_desc trees[2];
 		struct tree *tree;
@@ -411,7 +414,9 @@ static int merge_working_tree(struct checkout_opts *opts,
 		init_tree_desc(&trees[1], tree->buffer, tree->size);
 
 		ret = unpack_trees(2, trees, &topts);
-		if (ret == -1) {
+		if (ret != -1) {
+			reprime_cache_tree = 1;
+		} else {
 			/*
 			 * Unpack couldn't do a trivial merge; either
 			 * give up or do a real merge, depending on
@@ -455,6 +460,8 @@ static int merge_working_tree(struct checkout_opts *opts,
 		}
 	}
 
+	if (reprime_cache_tree)
+		prime_cache_tree(&active_cache_tree, new->commit->tree);
 	if (write_cache(newfd, active_cache, active_nr) ||
 	    commit_locked_index(lock_file))
 		die("unable to write new index file");
-- 
1.6.3.rc1.18.g66996
Previous: Junio C HamanoNext: Alex Riesen
Message 5 of 6 in “Revisiting cache-tree”
  1. 0/4 Revisiting cache-treeJunio C Hamano, Apr 20, 2009
  2. 1/4 read-tree A B: do not corrupt cache-treeJunio C Hamano, Apr 20, 2009
  3. 2/4 Move prime_cache_tree() to cache-tree.cJunio C Hamano, Apr 20, 2009
  4. 3/4 read-tree -m A B: prime cache-tree from the switched-to treeJunio C Hamano, Apr 20, 2009
  5. 4/4 checkout branch: prime cache-tree fullyJunio C Hamano, Apr 20, 2009
  6. Alex RiesenApr 20, 2009

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.