(hitted "send" too soon) Daniel Shahaf wrote on Wed, Aug 11, 2010 at 03:40:51 +0300: > For the last few weeks I've been working on the atomic-revprop branch. > > (Its goal is port the new svn_fs_change_rev_prop2() to libsvn_ra, which > should allow callers to specify both a value and an optional "previous > value" and have the revprop change atomic; see [1].) > > Currently, the API is implemented over all RA layers, and the test (prop 34) > passes. > > To extend svnsync to use the new API for acquiring locks,
To extend svnsync to use the new API for acquiring locks, I'd like to make the API guarantee which error code it returns in case the atomic expectation didn't match the actual value (if any) found. This requires some work on ra_dav client/server to make them pass the error code on the wire (like ra_svn already does) --- per earlier thread this week [2]. Until then, I have a working patch for svnsync, which --- until said ra_dav work is implemented --- relies on checking the error message (that's what I have available) rather than the error code. That patch is attached to the previous mail in this thread. (I'll commit that after the "check the error message" hack is removed.) That's all for now I suppose. A roadmap of the work can be found in BRANCH-README [3]. Daniel (who maintains an offline list of points he should test/review) > > > > [1] > http://thread.gmane.org/gmane.comp.version-control.subversion.devel/120330/focus=120416 [2] http://svn.haxx.se/dev/archive-2010-08/0225.shtml [3] http://svn.apache.org/repos/asf/subversion/branches/atomic-revprop/BRANCH-README