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

Re: Locking non-existent paths. Time to discuss.

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-03-16 20:36:48 CET

On Wed, 16 Mar 2005, Ben Collins-Sussman wrote:

> Question 1: Given that lock-null resources might exist, should svn
> clients be able to see them? And to what extent?
> * 'svnadmin lslocks' already shows them.
> * 'svn status -u' shows remote locks on real files. Should it
> also show remote lock-null objects? This may prove very
> difficult to do; lundblad is working on it.
The biggest problem here is that libsvn_wc/status.c is a little hard to
understand (at least for me). I am doing this.

> * should 'svn info URL' show lock information if URL is a
> lock-null resource? It would be easy to do.
> * should 'svn ls' (i.e. svn_ra_get_dir()) show lock-null resources?
I think this is easy if the locked non-existent paths or direct children
of some non-existent path. But you could also lock something not a direct
child. Should we return phantom intermidate paths? (I'm talking about the
--recursive case.)

> Question 2: Should the svn client (and API) be able to lock
> nonexistent paths?
A problem with this is that the current implementation of svn up removing
defunct tokens uses the editor and entryrops. If someone locks a
schedule-add path, then that lock becomes defunct, we'd want to remove
that lock token from the WC. The editor can't open an non-existent path.

If think this feature would be nice, but it isn't a show-stopper.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 16 20:34:14 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.