diff options
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 25 |
1 files changed, 25 insertions, 0 deletions
@@ -14,6 +14,18 @@ General deleted. * References should be parsed 'manually' to get around command invocation, but be sure to be able to read packed refs. + +Object +------ +* DataStream method should read the data itself. This would be easy once you have + the actul loose object, but will be hard if it is in a pack. In a distant future, + we might be able to do that or at least implement direct object reading for loose + objects ( to safe a command call ). Currently object information comes from + persistent commands anyway, so the penalty is not that high. The data_stream + though is not based on persistent commands. + It would be good to improve things there as cat-file keeps all the data in a buffer + before it writes it. Hence it does not write to a stream directly, which can be + bad if files are large, say 1GB :). * Effectively Objects only store hexsha's in their id attributes, so in fact it should be renamed to 'sha'. There was a time when references where allowed as well, but now objects will be 'baked' to the actual sha to assure comparisons work. @@ -45,6 +57,11 @@ Index creating several tree objects, so in the end it might be slower. Hmm, probably its okay to use the command unless we go c(++) +Remote +------ +* 'push' method needs a test, a true test repository is required though, a fork + of a fork would do :)! + Repo ---- * Nice fetch/pull handling, at least supported/wired throuhg to the git command @@ -61,5 +78,13 @@ Tree * Should return submodules during iteration ( identifies as commit ) * Work through test and check for test-case cleanup and completeness ( what about testing whether it raises on invalid input ? ). See 6dc7799d44e1e5b9b77fd19b47309df69ec01a99 + +Testing +------- +* Create a test-repository that can be written to and changed in addition to the normal + read-only testing scheme that operates on the own repository. Doing this could be a simple + as forking a shared repo in a tmp directory. In that moment, we probably want to + facility committing and checkouts as well. + - Use these tests for git-remote as we need to test push - Also assure that the test-case setup is a bit more consistent ( Derive from TestCase, possibly make repo a class member instead of an instance member |