svn commit: r1293108 - /subversion/branches/multi-layer-moves/subversion/libsvn_wc/wc_db.c

[st...@apache.org]

Author: stsp
Date: Fri Feb 24 07:15:25 2012
New Revision: 1293108

URL: http://svn.apache.org/viewvc?rev=1293108&view=rev
Log:
On the multi-layer-moves branch, tweak a docstring.

*  subversion/libsvn_wc/wc_db.c
   (moved_node_t): Explain the simple rewriting case, too.

Modified:
    subversion/branches/multi-layer-moves/subversion/libsvn_wc/wc_db.c

Modified: subversion/branches/multi-layer-moves/subversion/libsvn_wc/wc_db.c
URL: http://svn.apache.org/viewvc/subversion/branches/multi-layer-moves/subversion/libsvn_wc/wc_db.c?rev=1293108&r1=1293107&r2=1293108&view=diff
==============================================================================
--- subversion/branches/multi-layer-moves/subversion/libsvn_wc/wc_db.c (original)
+++ subversion/branches/multi-layer-moves/subversion/libsvn_wc/wc_db.c Fri Feb 24 07:15:25 2012
@@ -6290,9 +6290,13 @@ struct op_delete_baton_t {
   const char *moved_to_relpath; /* NULL if delete is not part of a move */
 };
 
-/* This structure is used while rewriting move information for
- * a node which becomes a nested moved node.
+/* This structure is used while rewriting move information for nodes.
+ * 
+ * The most simple case of rewriting move information happens when
+ * a moved-away subtree is moved again:  mv A B; mv B C
+ * The second move requires rewriting moved-to info at or within A.
  *
+ * Another case is where a node which becomes a nested moved node.
  * A nested move happens when a subtree child is moved before or after
  * the subtree itself is moved. For example:
  *   mv A/F A/G