[svk-commit] r2752 - branches/path-resolver

nobody at bestpractical.com nobody at bestpractical.com
Tue Apr 22 06:32:20 EDT 2008


Author: ruz
Date: Tue Apr 22 06:32:19 2008
New Revision: 2752

Modified:
   branches/path-resolver/README.path-resolver

Log:
* update README

Modified: branches/path-resolver/README.path-resolver
==============================================================================
--- branches/path-resolver/README.path-resolver	(original)
+++ branches/path-resolver/README.path-resolver	Tue Apr 22 06:32:19 2008
@@ -4,6 +4,28 @@
 You're MORE than welcome to add more cases, ideas and other things
 that may help... Questions are ok too.
 
+=head1 FIRST MILESTONE
+
+looked deeper in the code and decided that it's better to stop on following goals:
+
+1) For new files we can stop on "add" and "skip" actions.
+* this is implemented:
+** for every new node you're asked if you want to add it then parent
+   dirs that don't exist are added back.
+** if it's dir then you can add only dir itself, but as well you can
+   add it with all its children without questions
+
+2) For changes it's possible to use the resolver we already have.
+
+=head2 M1 TODO
+
+* resolver help
+* when you're deciding if you want to add dir w/o children then
+  you usually want to list all new nodes in the dir, something like
+  > a)add all, o)nly this, ..., l)ist [a]: l
+  X/file
+  X/dir/file
+  ...
 
 =head1 CASES
 
@@ -39,11 +61,3 @@
    that it's been merged from trunk/A...
 
 
-=head1 FIRST MILESTONE
-
-looked deeper in the code and decided that it's better to stop on following goals:
-
-1) For new files we can stop on "add" and "skip" actions.
-
-2) For changes it's possible to use the resolver we already have.
-


More information about the svk-commit mailing list