summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorSebastian Thiel <byronimo@gmail.com>2009-10-27 20:09:50 +0100
committerSebastian Thiel <byronimo@gmail.com>2009-10-27 20:09:50 +0100
commit5047344a22ed824735d6ed1c91008767ea6638b7 (patch)
treeb6adbc134e0f00fab877a4c3a5637c2899114b71 /TODO
parentef592d384ad3e0ead5e516f3b2c0f31e6f1e7cab (diff)
downloadgitpython-5047344a22ed824735d6ed1c91008767ea6638b7.tar.gz
Added testing frame for proper fetch testing to be very sure this works as expected. Plenty of cases still to be tested
Diffstat (limited to 'TODO')
-rw-r--r--TODO7
1 files changed, 7 insertions, 0 deletions
diff --git a/TODO b/TODO
index d841f774..4dced9c6 100644
--- a/TODO
+++ b/TODO
@@ -96,6 +96,9 @@ Refs
- NO: The reference dosnt need to know - in fact it does not know about the
main HEAD, so it may not use it. This is to be done in client code only.
Remove me
+* Reference.from_path may return a symbolic reference although it is not related
+ to the reference type. Split that up into two from_path on each of the types,
+ and provide a general method outside of the type that tries both.
Remote
------
@@ -104,6 +107,10 @@ Remote
* Fetch should return heads that where updated, pull as well.
* Creation and deletion methods for references should be part of the interface, allowing
repo.create_head(...) instaed of Head.create(repo, ...). Its a convenience thing, clearly
+* When parsing fetch-info, the regex will have problems properly handling white-space in the
+ actual head or tag name as it does not know when the optional additional message will begin.
+ This can possibly improved by making stronger assumptions about the possible messages or
+ by using the data from FETCH_HEAD instead or as additional source of information
Repo
----