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 2018/05/10 11:36:44 UTC

svn commit: r1831326 - /subversion/branches/tree-api/BRANCH-README

Author: julianfoad
Date: Thu May 10 11:36:44 2018
New Revision: 1831326

URL: http://svn.apache.org/viewvc?rev=1831326&view=rev
Log:
On the 'tree-api' branch: Update BRANCH-README.

Modified:
    subversion/branches/tree-api/BRANCH-README

Modified: subversion/branches/tree-api/BRANCH-README
URL: http://svn.apache.org/viewvc/subversion/branches/tree-api/BRANCH-README?rev=1831326&r1=1831325&r2=1831326&view=diff
==============================================================================
--- subversion/branches/tree-api/BRANCH-README (original)
+++ subversion/branches/tree-api/BRANCH-README Thu May 10 11:36:44 2018
@@ -1,7 +1,10 @@
-This 'tree-read-api' branch is a feature branch to develop a new API.
+This 'tree-api' branch is a feature branch to develop a new API.
 As a 'feature' branch, it is maintained by periodic 'catch-up' (aka
 'sync') merges from trunk, and may one day be reintegrated to trunk.
 
+See:
+  https://cwiki.apache.org/confluence/display/SVN/Common+Tree+Interfaces
+
 The new API is an abstraction of a generic tree of (usually) versioned
 nodes -- where each node is a file or directory, with properties.  We
 already have a generic tree-editing API (svn_delta_editor_t,
@@ -22,8 +25,3 @@ two arbitrary trees, related or not, suc
 of doing this by writing several more variants of the current three
 subroutines (WC/WC, WC/repos, repos/repos), in principle we would need
 just one diff subroutine that takes two Tree objects as input.
-
-Another goal here is to facilitate writing a three-way merge that fully
-supports moves and renames.
-
-- Julian Foad, November 2012