Revision 83ae209bf9708bf1b67dbac4a3629a0003af5dbb authored by Junio C Hamano on 20 April 2009, 10:58:20 UTC, committed by Junio C Hamano on 20 April 2009, 11:16:42 UTC
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>
1 parent 456156d
| File | Mode | Size |
|---|---|---|
| diff.0-1 | -rw-r--r-- | 49 bytes |
| diff.0-2 | -rw-r--r-- | 77 bytes |
| diff.0-3 | -rw-r--r-- | 80 bytes |
| diff.1-0 | -rw-r--r-- | 49 bytes |
| diff.1-2 | -rw-r--r-- | 80 bytes |
| diff.1-3 | -rw-r--r-- | 80 bytes |
| diff.2-0 | -rw-r--r-- | 77 bytes |
| diff.2-1 | -rw-r--r-- | 80 bytes |
| diff.2-3 | -rw-r--r-- | 77 bytes |
| diff.3-0 | -rw-r--r-- | 80 bytes |
| diff.3-1 | -rw-r--r-- | 80 bytes |
| diff.3-2 | -rw-r--r-- | 77 bytes |
Computing file changes ...
