@matheusbsbs / matheus-bagliano / commits / 8b9b0f3af7
Fork 0

"Assume unchanged" git: do not set CE_VALID with --refresh

When working with automatic assume-unchanged mode using core.ignorestat, setting CE_VALID after --refresh makes things more cumbersome to use. Consider this scenario: (1) the working tree is on a filesystem with slow lstat(2). The user sets core.ignorestat = true. (2) "git checkout" to switch to a different branch (or initial checkout) updates all paths and the index starts out with "all clean". (3) The user knows she wants to edit certain paths. She uses update-index --no-assume-unchanged (we could call it --edit; the name is inmaterial) to mark these paths and starts editing. (4) After editing half of the paths marked to be edited, she runs "git status". This runs "update-index --refresh" to reduce the false hits from diff-files. (5) Now the other half of the paths, since she has not changed them, are found to match the index, and CE_VALID is set on them again. For this reason, this commit makes update-index --refresh not to set CE_VALID even after the path without CE_VALID are verified to be up to date. The user still can run --really-refresh to force lstat() to match the index entries to the reality. Signed-off-by: Junio C Hamano <junkio@cox.net>

Junio C Hamano committed Feb 8, 2006 at 21:49 UTC 8b9b0f3af73233595b6b1103ffb30242508a5e47
1 file changed +9
update-index.c
+9
@@ -172,6 +172,15 @@ static struct cache_entry *refresh_entry(struct cache_entry *ce, int really)
172 memcpy(updated, ce, size);
173 fill_stat_cache_info(updated, &st);
174
175 + /* In this case, if really is not set, we should leave
176 + * CE_VALID bit alone. Otherwise, paths marked with
177 + * --no-assume-unchanged (i.e. things to be edited) will
178 + * reacquire CE_VALID bit automatically, which is not
179 + * really what we want.
180 + */
181 + if (!really && assume_unchanged && !(ce->ce_flags & htons(CE_VALID)))
182 + updated->ce_flags &= ~htons(CE_VALID);
183 +
184 return updated;
185 }
186