# 
# 
# patch "TODO"
#  from [e608772ab5779f323dddcee683d6c5a826bbf84e]
#    to [9caf49f2ed434f3943a89b627d974c02f597ed49]
# 
============================================================
--- TODO	e608772ab5779f323dddcee683d6c5a826bbf84e
+++ TODO	9caf49f2ed434f3943a89b627d974c02f597ed49
@@ -1,12 +1,19 @@ NEW VERSION
 
 NEW VERSION
 
  * Fix the RSS date fields
+ * Highlight -> content_type mapping (works at the moment, somehow)
  * JSON
- * Highlight -> content_type mapping (works at the moment, somehow)
+ * Unit tests
+ * Read-only WebDAV support
+ * Put copyright notices on the files, mostly so I can keep track 
+   of where they end up.
  
 BUGS:
 
+ * HEAD just does GET; we should really do HEAD properly. Also, we 
+   should start issuing eTags
+
 TODO:
 
   * support for translation, and see if we can get some people to help with that
@@ -24,16 +31,6 @@ TODO:
     which updates with the commands that have been run - useful for debugging, 
     also useful for beginners to see how to do stuff.
 
-  * Use monotone automate graph to do the ancestry graphing, and show some 
-    future information. Perhaps cache based on the mtime of the db viewmtn 
-    is looking at? Might be good enough.
-
-    Show dotted lines for propogates (with that information on the arc)
-    
-    Show lines leading off from the boxes at either end of the graph (if 
-    applicable) to give context that the image being shown is part of a 
-    large overall graph.
-
   * Show information when mousing over long hex strings.
 
   * Magically make http:// ftp:// etc links inside files clickable
@@ -43,20 +40,10 @@ TODO:
     explain what's happened. For bonus points, index into the diff so you 
     can click on a file that changed and jump to that section in the diff.
 
-  * Improve the file listing; use data from the new rosters branch 
-    to get a better idea of when a given file was last touched.
-
   * When viewing a file, give a list of revisions in which that file 
     was recently changed. Include in the list a link to diff with each 
     revision.
 
-  * generally clean up table formatting code; things like
-      list_of_branches()
-      list_of_tags()
-      revision_certs()
-      revision_details()
-    use a generic method to output the tables
-
   * from [mrb]
     support for multiple databases (perhaps some sort of dropdown to say which 
     database you want to look in) - perhaps also make the branches page show the 
@@ -84,10 +71,3 @@ AJAX ideas:
   * we need some concept of selecting two points revisions for diffs or other 
     comparison. This is the main strength ViewCVS seems to have over us.
 
-LONG TERM:
-
-  * provide some option for people without apache2 / mod_python to run the 
-    thing; even if it's running the program from a standalone python webserver.
-    Would settle for a solution that required a cgi capable webserver rather than 
-    specifically mod_python (and thus apache2) while still supporting mod_python 
-    acceleration if present.