[Pkg-bazaar-commits] ./bzr/unstable r552: - update todo list

[Martin Pool]

------------------------------------------------------------
revno: 552
committer: Martin Pool <mbp at sourcefrog.net>
timestamp: Wed 2005-05-25 13:04:47 +1000
message:
  - update todo list
modified:
  TODO
-------------- next part --------------
=== modified file 'TODO'
--- a/TODO	2005-05-24 21:14:28 +0000
+++ b/TODO	2005-05-25 03:04:47 +0000
@@ -71,10 +71,6 @@
 * ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
   giving options to display ids, types, etc.
 
-* Atomic file class that renames into place when it's closed.
-
-* Don't abort if ``~/.bzr.log`` can't be used.
-
 * Split BzrError into various more specific subclasses for different
   errors people might want to catch.
 
@@ -96,13 +92,6 @@
 Medium things
 -------------
 
-* Change command functions into Command() objects, like in hct, and
-  then the grammar can be described directly in there.  Since all
-  option definitions are global we can define them just once and
-  reference them from each command.
-
-* Merge Aaron's merge code.
-
 * Merge revert patch.
 
 * ``bzr mv`` that does either rename or move as in Unix.
@@ -116,7 +105,9 @@
 
 * Fix up Inventory objects to represent root object as an entry.
 
-* Don't convert entire entry from 
+* Don't convert entire entry from ElementTree to an object when it is
+  read in, but rather wait until the program actually wants to know
+  about that node.
 
 * Extract changes from one revision to the next to a text form
   suitable for transmission over email.
@@ -130,9 +121,6 @@
 
 * Write a reproducible benchmark, perhaps importing various kernel versions.
 
-* Change test.sh from Bourne shell into something in pure Python so
-  that it can be more portable.
-
 * Directly import diffs!  It seems a bit redundant to need to rescan
   the directory to work out what files diff added/deleted/changed when
   all the information is there in the diff in the first place.
@@ -248,8 +236,6 @@
   urlgrabber's docs say they are working on batched downloads; we
   could perhaps ride on that or just create a background thread (ew).
 
-* Should be a signature at the top of the cache file.
-
 * Paranoid mode where we never trust SHA-1 matches.
 
 * Don't commit if there are no changes unless forced.