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

Re: DAV unlock problem.

From: Peter Lundblad <peter_at_famlundblad.se>
Date: 2006-03-02 22:22:51 CET

Justin Erenkrantz writes:
> On 2/15/06, Alexander Kitaev <alex@tmate.org> wrote:
> > First:
> >
> > PROPFIND to get lock-token (lockdiscovery) is always sent on "svn unlock",
> > independently on whether there is lock token in the working copy or not. As
> > PROPFIND is sent just before "UNLOCK" I suppose that "token" passed
> > toshim_svn_ra_dav_ _unlock is always NULL.
> No, it's svn_client_unlock that is fetching the locks well before
> ra_dav's unlock function is executed (see line 501). I'm not real
> clear why we *need* to fetch the tokens from the server if we have it
> already in the WC though.

That's a bug in the client code whitch was introduced late in the
locking branch. XFail test committed in r18691. Working on the fix.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 2 22:23:51 2006

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