[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [atomic-revprops] status update

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Tue, 10 Aug 2010 20:10:54 -0500

On Tue, Aug 10, 2010 at 7:51 PM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> (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].

Do you think the work is sufficiently non-disruptive to be moved back to trunk?

-Hyrum
Received on 2010-08-11 03:11:34 CEST

This is an archived mail posted to the Subversion Dev mailing list.