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

"Peter N. Lundblad" <peter@famlundblad.se> writes:

> > * '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.

Er. Sorry about that. :-)

> > * 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.)

I think you meant:

   I think this is easy if the locked non-existent paths are direct
   children of some existent path.

Making this a requirement is, in my opinion, the difference between
infeasible/insane and feasible/sane.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 16 21:04:43 2005