summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorSebastian Thiel <byronimo@gmail.com>2009-10-21 23:11:40 +0200
committerSebastian Thiel <byronimo@gmail.com>2009-10-21 23:11:40 +0200
commit7b50af0a20bcc7280940ce07593007d17c5acabd (patch)
treea69e76cb1911f7098fded9a728229d2f119718cd /TODO
parent6662422ba52753f8b10bc053aba82bac3f2e1b9c (diff)
downloadgitpython-7b50af0a20bcc7280940ce07593007d17c5acabd.tar.gz
index: Added write_tree method including test
Diffstat (limited to 'TODO')
-rw-r--r--TODO13
1 files changed, 7 insertions, 6 deletions
diff --git a/TODO b/TODO
index 460780d3..14d65e26 100644
--- a/TODO
+++ b/TODO
@@ -37,12 +37,13 @@ Overhaul docs - check examples, check looks, improve existing docs
Index
-----
-* Index class required for special handling ? Probably considering what I want
- to do ! Dulwich can already write the index, and read trees, although it
- could be improved as well and could possibly be made faster unless we want
- to use the c modules ( not for now )
-* Index Merge ( merge two trees into the index to quickly see conflicts ).
- Its possible to write it into a separate index file that can be read separately.
+* write_tree should write a tree directly, which would require ability to create
+ objects in the first place. Should be rather simple as it is
+ "tree" bytes datablock | sha1sum and zipped.
+ Currently we use some file swapping and the git command to do it which probably
+ is much slower. The thing is that properly writing a tree from an index involves
+ creating several tree objects, so in the end it might be slower.
+ Hmm, probably its okay to use the command unless we go c(++)
Repo
----