Hello All,
I've found two related problems with "svn unlock" over DAV (Subversion
1.3.0, both server and client are on Windows XP):
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.
Second:
Sending UNLOCK with obsolete lock-token causes server to respond with 400
HTTP status, without any meaningful error message inside.
Should I submit these to the issues tracker?
Alexander Kitaev,
TMate Software,
http://tmate.org/
http://jetbrains.com/tmate/
> -----Original Message-----
> From: Philip Martin [mailto:philip@codematters.co.uk]
> Sent: Wednesday, February 15, 2006 10:58 PM
> To: Garrett Rooney
> Cc: Kamesh Jayachandran; SVN Dev
> Subject: Re: [PATCH] To automate the svnsshcheck
>
> Garrett Rooney <rooneg@electricjellyfish.net> writes:
>
> > It's not just a matter of it cleaning up after itself, I'm
> > uncomfortable having it mess around in .ssh at all.
>
> Me too. Also, it probably won't work if someone tries to run
> multiple instances of the testsuite simultaneously.
>
> --
> Philip Martin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 15 21:20:17 2006