summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorSebastian Thiel <byronimo@gmail.com>2009-11-03 19:49:38 +0100
committerSebastian Thiel <byronimo@gmail.com>2009-11-03 19:49:38 +0100
commite648efdcc1ca904709a646c1dbc797454a307444 (patch)
tree1643094b3367c6c087e5e5ee2cb402c8318ce1e9 /TODO
parent9b426893ce331f71165c82b1a86252cd104ae3db (diff)
downloadgitpython-e648efdcc1ca904709a646c1dbc797454a307444.tar.gz
remotes are now retrieved directly by parsing the repository configuration file. This removes a git command invocation
Diffstat (limited to 'TODO')
-rw-r--r--TODO9
1 files changed, 4 insertions, 5 deletions
diff --git a/TODO b/TODO
index a350bf55..dc87c8b6 100644
--- a/TODO
+++ b/TODO
@@ -13,8 +13,6 @@ General
the std-in command types, as it appears they are not killed when the repo gets
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.
Object
------
@@ -83,6 +81,7 @@ Refs
* For performance reasons it would be good to reimplement git-update-ref to be
fully equivalent to what the command does. Currently it does some checking and
handles symbolic refs as well as normal refs, updating the reflog if required.
+ Its low-priority though as we don't set references directly that often.
* I have read that refs can be symbolic refs as well which would imply the need
to possibly dereference them. This makes sense as they originally where possibly
a symbolic link. This would mean References could be derived from SymbolicReference
@@ -90,11 +89,11 @@ Refs
* Making the reflog available as command might be useful actually. This way historical
references/commits can be returned. Git internally manages this if refs are specified
with HEAD@{0} for instance
-
+* References should be parsed 'manually' to get around command invocation, but
+ be sure to be able to read packed refs.
+
Remote
------
-* iter_items should parse the configuration file manually - currently a command
- is issued which is much slower than it has to be ( compared to manual parsing )
* When parsing fetch-info, the regex will not allow spaces in the target remote ref as
I couldn't properly parse the optional space separated note in that case. Probably
the regex should be improved to handle this gracefully.