[Zope3-checkins] CVS: Zope3/src/zope/fssync - README.txt:1.5

[Guido van Rossum]

Update of /cvs-repository/Zope3/src/zope/fssync
In directory cvs.zope.org:/tmp/cvs-serv9571

Modified Files:
	README.txt 
Log Message:
Refactor BUGS and TO DO lists.


=== Zope3/src/zope/fssync/README.txt 1.4 => 1.5 ===
--- Zope3/src/zope/fssync/README.txt:1.4	Tue May 13 17:59:02 2003
+++ Zope3/src/zope/fssync/README.txt	Wed May 14 10:55:40 2003
@@ -57,13 +57,13 @@
 * After update or commit for a single file, the other files and
   directories in the same directory are silently removed!!!!
 
+* After committing an added or removed dict, the flag doesn't get
+  cleared in the entry.
+
 
 TO DO
 -----
 
-* after committing an added or removed file, the flag doesn't get
-  cleared in the entry
-
 * unit tests for the fssync core functionality
 
 * refactoring more of the fssync core functionality
@@ -79,37 +79,38 @@
   -N shows diffs for added/removed files as diffs with /dev/null
   more GNU diff options?  e.g. --ignore-space-change etc.
 
+* allow checking out the root
 
-Jim's TO DO
------------
+* allow checking out /++etc++site
 
-Here's the TO DO list from zope3/doc/TODO.txt:
+* add adapters for more common content types, e.g. images
 
-  - Client command-line tool w HTTP-based interface to server
-    that provided CVS-like interface and features. Including:
+* add a log message to the commit command
 
-    - checkout and commit
+* commit shouldn't commit new versions of unchanged objects to ZODB
 
-    - update including merge and offline version
+* refine the adapter protocol or implementation to leverage the
+  file-system representation protocol
+
+
+TO DO LATER
+-----------
 
-    - diff and offline diff
+* Work out security details.
 
-  - Refine the adapter protocol or implementation to leverage
-    the file-system representation protocol.
+* In common case where extra data are simple values, store extra data
+  in the entries file to simplify representation and updates.  Maybe
+  do something similar w annotations.
 
-  - Maybe leverage adaptable storage ideas to assure
-    losslessness.
+* Maybe do some more xmlpickle refinement with an eye toward
+  impproving the usability of simple dictionary pickles.
 
-  - In common case where extra data are simple values, store
-    extra data in the entries file to simplify representation
-    and updates.  Maybe do something similar w annotations.
+* Maybe leverage adaptable storage ideas to assure losslessness.
 
-  - Maybe do some more xmlpickle refinement with an eye toward
-    impproving the usability of simple dictionary pickles.
+* Export and import as a special case.
 
-  - export and import as a special case
+* Improve some common data file formats (e.g. simplify entries file).
 
-  - Improve some common data file formats (e.g. simplify
-    entries file).
+* Commit to multiple Zope instances?
 
-  - Work out security details
+* Diff/merge multiple working sets (a la bitkeeper)?