subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From julianf...@apache.org
Subject svn commit: r1683287 - /subversion/branches/move-tracking-2/BRANCH-README
Date Wed, 03 Jun 2015 11:17:43 GMT
Author: julianfoad
Date: Wed Jun  3 11:17:43 2015
New Revision: 1683287

URL: http://svn.apache.org/r1683287
Log:
On the 'move-tracking-2' branch: Update BRANCH-README.

* BRANCH-README
  Update the description of 'svnmover'.

Modified:
    subversion/branches/move-tracking-2/BRANCH-README

Modified: subversion/branches/move-tracking-2/BRANCH-README
URL: http://svn.apache.org/viewvc/subversion/branches/move-tracking-2/BRANCH-README?rev=1683287&r1=1683286&r2=1683287&view=diff
==============================================================================
--- subversion/branches/move-tracking-2/BRANCH-README (original)
+++ subversion/branches/move-tracking-2/BRANCH-README Wed Jun  3 11:17:43 2015
@@ -52,17 +52,21 @@ Work on this branch:
     which branching and moving are significant, to see what we expect
     and see if we can write code that delivers it.
 
-    'svnmover' operates directly on a repo, like 'svnmucc'. Working copy
-    considerations -- mixed-rev states, sparse checkouts, conflicts, and
-    so on -- are completely avoided. A working copy is, in essence, a tool
-    for viewing and making changes to the versioned data, and so needs to
-    be designed to support the versioned data model. That comes *after*
-    designing the data model. Working copy considerations may be introduced
-    to 'svnmover' in due course in order to explore how they would work.
-
-    'svnmover' processes a series of commands given on the command line, and
-    then commits the result. In interactive mode (when run with no command
-    arguments) it makes one commit per line of input.
+    'svnmover' operates directly on a repo, like 'svnmucc', without using
+    a working copy on disk. However, it simulates a short-lived working
+    copy, in memory. It processes a series of commands given on the command
+    line or interactively. These commands change the state of the simulated
+    WC. The changes are committed on exit or whenever the 'commit' command
+    is given.
+
+    Advanced working copy facilities -- mixed-rev states, sparse checkouts,
+    conflicts, and so on -- are initially not supported. Such facilities
+    may be introduced to 'svnmover' in due course in order to explore how
+    they would work.
+
+    (A working copy is, in essence, a tool for viewing and making changes
+    to the versioned data, and so its facilities need to be redesigned to
+    support the new versioned data model.)
 
     The implementation stores metadata either in revprops or in flat files
     in the repository directory; the metadata is the same in either case.
@@ -76,6 +80,8 @@ Work on this branch:
       branching: branch, create new branch, list branches
       diff
       merge
+      commit
+      update
 
     UI things to do:
       add a 'parallel mode' UI as an alternative to the sequential mode
@@ -84,17 +90,6 @@ Work on this branch:
 
     Bigger things to do:
 
-      Build a mock WC:
-
-        1. "Check out" a given rev by starting an in-memory txn based
-          on that rev.
-
-        2. Make edits in this txn.
-
-        3. Start a commit, get a new txn based on repository head.
-
-        4. Replay the WC txn's changes into the commit txn, and commit it.
-
       "Replay" API: convert committed changes to an edit drive
 
         * A txn must keep track of which EIDs in it were previously



Mime
View raw message