You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by ju...@apache.org on 2013/05/22 20:44:35 UTC

svn commit: r1485329 - /subversion/branches/move-tracking-1/BRANCH-README

Author: julianfoad
Date: Wed May 22 18:44:35 2013
New Revision: 1485329

URL: http://svn.apache.org/r1485329
Log:
On the move-tracking-1 branch: add a BRANCH-README file.

Added:
    subversion/branches/move-tracking-1/BRANCH-README   (with props)

Added: subversion/branches/move-tracking-1/BRANCH-README
URL: http://svn.apache.org/viewvc/subversion/branches/move-tracking-1/BRANCH-README?rev=1485329&view=auto
==============================================================================
--- subversion/branches/move-tracking-1/BRANCH-README (added)
+++ subversion/branches/move-tracking-1/BRANCH-README Wed May 22 18:44:35 2013
@@ -0,0 +1,47 @@
+This is a development branch, intended for prototyping ideas around move
+tracking, with an emphasis on the client side and how move information can
+be used in merging.
+
+The branch should be maintained with catch-up merges from trunk.
+
+The branch should NOT be merged back to trunk.
+
+The code on this branch should build but need not pass testing at all times.
+
+Everything documented here is subject to change from time to time.
+
+
+== Main Goals ==
+
+  * Discover which APIs and API concepts will be affected by move tracking:
+    which need to be modified to maintain backward compatibility, and which
+    need to be extended to handle moves.  See
+    <http://wiki.apache.org/subversion/MergeDev/ApiChangesForMove>.
+
+  * Establish how to feed move information into diff and merge.
+
+  * Keep backward compatibility.
+
+
+== Non-Goals for This Branch ==
+
+  * FSFS storage format.
+
+  * APIs at libsvn_repos, libsvn_fs and libsvn_fs_fs.
+
+  * Wire protocols.
+
+  * A new merge algorithm.
+
+
+== Tasks and Changes ==
+
+  * Implement simple move tracking in FSFS, sufficient to provide move
+    information on demand.  (An alternative would be to implement heuristic
+    move detection.) [STARTED]
+
+  * Create a tree-diff representation to include move information.  Perhaps
+    based on svn_diff_tree_processor_t, svn_delta_editor_t or Ev2.  The move
+    information may be in the form of a list of matching node pairs.
+
+  * ...

Propchange: subversion/branches/move-tracking-1/BRANCH-README
------------------------------------------------------------------------------
    svn:eol-style = native