From 20c34a929a8b2871edd4fd44a38688e8977a4be6 Mon Sep 17 00:00:00 2001 From: Sebastian Thiel Date: Thu, 22 Oct 2009 17:40:04 +0200 Subject: =?UTF-8?q?Added=20reset=20method=20to=20Head=20-=20its=20a=20clas?= =?UTF-8?q?s=20method=20due=20to=20the=20very=20general=20nature=20of=20th?= =?UTF-8?q?e=20command.=20Yet=20I=20don't=20really=20like=20the=20way=20yo?= =?UTF-8?q?u=20have=20to=20call=20it=20as=20repo=20has=20to=20be=20?= =?UTF-8?q?=E1=B9=95assed=20as=20first=20arg?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- TODO | 15 +++------------ 1 file changed, 3 insertions(+), 12 deletions(-) (limited to 'TODO') diff --git a/TODO b/TODO index afda659a..db77df67 100644 --- a/TODO +++ b/TODO @@ -11,7 +11,8 @@ General a sha or ref unless cat-file is used where it must be a sha * Overhaul command caching - currently its possible to create many instances of the std-in command types, as it appears they are not killed when the repo gets - deleted. + deleted. A clear() method could already help to allow long-running programs + to remove cached commands after an idle time. * References should be parsed 'manually' to get around command invocation, but be sure to be able to read packed refs. @@ -64,7 +65,6 @@ Remote Repo ---- -* Nice fetch/pull handling, at least supported/wired throuhg to the git command * Blame: Read the blame format making assumptions about its structure, currently regex are used a lot although we can deduct what will be next. - Read data from a stream directly from git command @@ -78,13 +78,4 @@ 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 + -- cgit v1.2.3