Jeff King <peff@xxxxxxxx> writes: > ... I notice there is > a return very early on in update_one() when has_sha1_file() matches, and > it seems like that would trigger in some interesting cases, too. Yeah, I missed that. It says "we were asked to update one cache_tree that corresponds to this subdirectory, found that hashes everything below has been rolled up and still valid, and we already have the right tree object in the object store". It can simply become freshen(), which is "do we have it in the object store?" with a side effect of touching iff the answer is "yes".