You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by gs...@apache.org on 2010/02/20 18:17:30 UTC
svn commit: r912152 - /subversion/trunk/notes/wc-ng/transitions
Author: gstein
Date: Sat Feb 20 17:17:29 2010
New Revision: 912152
URL: http://svn.apache.org/viewvc?rev=912152&view=rev
Log:
* notes/wc-ng/transitions:
(key): would be nice to specifically denote "not allowed" operations
(excluded question): provide an (IMO) answer
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=912152&r1=912151&r2=912152&view=diff
==============================================================================
--- subversion/trunk/notes/wc-ng/transitions (original)
+++ subversion/trunk/notes/wc-ng/transitions Sat Feb 20 17:17:29 2010
@@ -115,6 +115,9 @@
- : operation not allowed or no change required
x : original state not allowed
+### it would be nice to call out the operations that are "not allowed"
+
+
notes
-----
[1] <none> if the root of the copy, not-present otherwise.
@@ -140,3 +143,11 @@
against. If commit doesn't automatically delete the node can the user
delete it in the working tree? Like WORKING_NODE.presence incomplete
the problem is that revert would not be able to cope.
+
+### gstein sez: commit should NOT do a deletion for an excluded node.
+### the presence is typically used for (say) copying a large tree,
+### and then excluding the subtree within the copy from the working
+### copy. maybe the user doesn't want all that stuff there. at
+### commit time, the copy is performed, and nothing more. if you
+### wanted to delete this node, then switch it to depth=empty
+### and presence=not-present.