Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> writes: > (In fact, it might be perfectly fine to have just a *single* cache, which > is keyed on the dirname of the pathname: if the dirname changes, just > throw the cache away, and read it in from all the subdirectories leading > to that directory - you'd still re-read stuff, but all the common cases > will walk the directory structure in a nice pattern, so you'd have a very > simple cache that actually gets good cache hit behaviour) I'd agree that we can start with just a single one at the toplevel and if somebody wants to extend it we can do so later. >> One thing that might be tricky is what should be done while making a >> merge or checking out from a tree. Ideally, the information should be >> read from the tree that is being extracted, but that would make the >> code structure a little bit, eh, "interesting". > > No, that would be pretty horrid. So just tell everybody that it's based on > the working tree. I don't think it's likely to be a problem in practice. Except for the initial checkout... - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html