On May 23, 2005, at 10:46 AM, Philip Martin wrote:
>
> The bug is in svn_client_lock. What goes wrong is that 'svn lock'
> starts with the URL of the common ancestor and generates target URLs
> by appending relative wc paths. So in your example lock works because
>
> URL of www + relative path of www/faq.html == URL of www/faq.html
>
> Switch allows working copies where that relation is not true, and then
> lock may operate on the wrong URL, it might even fail if the derived
> URL doesn't exist. With multiple lock targets the problem gets worse,
> the URL of the common ancestor of the wc paths might not be the common
> ancestor of the URLs.
Wow, how nasty.
So what's the proper algorithm, then? It seems like we should
harvest all the URLs of the targets directly from the entries files,
then find the common ancestor of the URL-set.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 23 18:43:53 2005