Re: Unresolved issues
- From
Junio C Hamano <junkio@cox.net>
- Date
- Feb 20, 2007, 21:43 UTC
- Message-ID
- <7vfy90v729.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <Pine.LNX.4.64.0702200934270.20368@woody.linux-foundation.org>
Linus Torvalds <torvalds@linux-foundation.org> writes:
Show 6 quoted lines
> (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.
Show 7 quoted lines
>> 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...