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

Guido van Rossum guido@python.org
Wed, 28 May 2003 15:19:15 -0400


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

Modified Files:
	README.txt 
Log Message:
Fixed the last bug.  Updated TODO list.


=== Zope3/src/zope/fssync/README.txt 1.11 => 1.12 ===
--- Zope3/src/zope/fssync/README.txt:1.11	Wed May 28 14:03:27 2003
+++ Zope3/src/zope/fssync/README.txt	Wed May 28 15:19:14 2003
@@ -54,34 +54,32 @@
 BUGS
 ----
 
-* Sometimes when committing additions or removals, the Entries.xml
-  file doesn't get updated properly.
+* See TO DO below.
 
 
 TO DO
 -----
 
-* more unit tests for fsmerge, to check that entries are handled
-  correctly in all cases (including addition/deletion/change of
-  type).
+* Unit tests for the fssync core functionality.
 
-* unit tests for the fssync core functionality
+* More refactoring and cleanup of the fssync core functionality.
 
-* more refactoring and cleanup of the fssync core functionality
+* Implement diff using difflib.
 
-* more diff options:
+* More diff options:
   -2 diffs between local and remote
   -3 diffs between original and remote
   -N shows diffs for added/removed files as diffs with /dev/null
-  more GNU diff options?  e.g. --ignore-space-change etc.
 
-* something akin to cvs -n update, which shows what update would do
-  without actually doing it
+* More GNU diff options?  e.g. --ignore-space-change etc.
 
-* refine the adapter protocol or implementation to leverage the
-  file-system representation protocol
+* Something akin to cvs -n update, which shows what update would do
+  without actually doing it.
 
-* use camelCase for method names
+* Refine the adapter protocol or implementation to leverage the
+  file-system representation protocol.
+
+* Use camelCase for method names.
 
 
 TO DO LATER
@@ -94,7 +92,7 @@
   do something similar w annotations.
 
 * Maybe do some more xmlpickle refinement with an eye toward
-  impproving the usability of simple dictionary pickles.
+  improving the usability of simple dictionary pickles.
 
 * Maybe leverage adaptable storage ideas to assure losslessness.