Re: Adding a new file as if it had existed
- From
Andreas Ericsson <ae@op5.se>
- Date
- Dec 13, 2006, 09:40 UTC
- Message-ID
- <457FCA8C.6000300@op5.se>
- In-Reply-To
- <7vzm9tuft7.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
Show 17 quoted lines
> "Bahadir Balban" <bahadir.balban@gmail.com> writes: > > There is one thing we could further optimize, though. > > Switching branches with 100k blobs in a commit even when there > are a handful paths different between the branches would still > need to populate the index by reading two trees and collapsing > them into a single stage. In theory, we should be able to do a > lot better if two-tree case of read-tree took advanrage of > cache-tree information. If ce_match_stat() says Ok for all > paths in a subdirectory and the cached tree object name for that > subdirectory in the index match what we are reading from the new > tree, we should be able to skip reading that subdirectory (and > its subdirectories) from the new tree object at all. > > Anybody interested to give it a try? >
I'm not vell-versed enough in git internals to have my hopes high of making something useful of it, but if you give me a pointer of where to start I'd be happy to try, and perhaps learn something in the process.
-- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se