Author: brane
Date: Sun Mar 30 09:27:43 2014
New Revision: 1583113

URL: http://svn.apache.org/r1583113
Log:
On the remote-only-status branch: Describe new solution.

* BRANCH-README: Update branch description.

Modified:
    subversion/branches/remote-only-status/BRANCH-README

Modified: subversion/branches/remote-only-status/BRANCH-README
URL: 
http://svn.apache.org/viewvc/subversion/branches/remote-only-status/BRANCH-README?rev=1583113&r1=1583112&r2=1583113&view=diff
==============================================================================
--- subversion/branches/remote-only-status/BRANCH-README (original)
+++ subversion/branches/remote-only-status/BRANCH-README Sun Mar 30 09:27:43 
2014
@@ -5,14 +5,15 @@ Subversion's "svn status --update" comma
 status with the latest state of the repository. Long-running clients,
 such as TortoiseSVN or SmartSVN, which cache working copy state, would
 benefit from a version of the svn_client_status API that compares
-repository status to the WC BASE tree, ignoring any local
-modifications. Whilst these clients could drive the svn_ra_do_status
-API directly (and do, at least in the case of SmartSVN 8.5 and later);
-however, they do not get enough information from status and/or info to
-be able to properly account for nodes omitted from sparse working
-copies, which may result in lots of extraneous data being sent from
-the server.
+repository status to the state in the working copy database, ignoring
+any unrecorded local modifications and omitting the usual scan of the
+working copy. Whilst these clients could drive the svn_ra_do_status
+API directly (and do, at least in the case of SmartSVN 8.5 and later),
+they do not get enough information from status and/or info to be able
+to properly account for nodes omitted from sparse working copies,
+which may result in lots of extraneous data being sent from the
+server.
 
 This branch is an ongoing research into implementing a variant of the
-svn_client_status API that drives the status editor using informatino
-only about the BASE tree in wc.db, and does not touch the file system.
\ No newline at end of file
+svn_client_status API that drives the status editor using only
+information in wc.db, and does not touch the file system.
\ No newline at end of file


Reply via email to