svn commit: r915750 - /subversion/trunk/notes/wc-ng/transitions

[ph...@apache.org]

Author: philip
Date: Wed Feb 24 11:19:28 2010
New Revision: 915750

URL: http://svn.apache.org/viewvc?rev=915750&view=rev
Log:
* notes/wc-ng/transitions: More about working presence.

Modified:
    subversion/trunk/notes/wc-ng/transitions

Modified: subversion/trunk/notes/wc-ng/transitions
URL: http://svn.apache.org/viewvc/subversion/trunk/notes/wc-ng/transitions?rev=915750&r1=915749&r2=915750&view=diff
==============================================================================
--- subversion/trunk/notes/wc-ng/transitions (original)
+++ subversion/trunk/notes/wc-ng/transitions Wed Feb 24 11:19:28 2010
@@ -15,8 +15,14 @@
 There are 6 possible WORKING_NODE.presence values:
   normal, incomplete, absent, excluded, not-present, base-deleted
 in addition to <none> when the WORKING_NODE does not exist.
-A comment in 'wc-metadata.sql' says not all of those are allowed, but
-it may be wrong.
+
+### A comment in 'wc-metadata.sql' says not all of 6 values are
+allowed in WORKING, but it may be wrong.  A wc-to-wc copy could have
+absent and excluded presence values in the BASE source, does the copy
+put those values into the working tree?  An url-to-wc copy could get
+an authz failure part way through, does that result in an absent node?
+There is currently no UI to do a sparse url-to-wc copy, but if there
+was then would that result in an excluded node?
 
 When removing a WORKING_NODE any ACTUAL_NODE is also removed.