index.write_tree: now uses MemoryDB, making tree handling more efficient as IO will only be done when required. A possible disadvantage though is that time is spent on compressing the trees, although only the raw data and their shas would theoretically be needed. On the other hand, compressing their data uses less memory. An optimal implementation would just sha the data, check for existance, and compress it to write it to the database right away. This would mean more specialized code though, introducing redundancy. If IStreams would know whether they contain compressed or uncompressed data, and if there was a method to get a sha from data, this would work nicely in the existing framework though

1 files changed, 0 insertions, 0 deletions

diff --git a/lib/git/ext/gitdb b/lib/git/ext/gitdb
-Subproject 92ca2e4ad606fbec7c934ad9e467a1b51fddcc9
+Subproject 9b53ab02cb44571e6167a125a5296b7c3395563