Does locking feature imply need for 'svn release'?

I'm forwarding this exchange from the users@ list:

Greg Thomas <thomasgd@omc.bt.co.uk> writes:
> On Tue, 8 Feb 2005 11:08:21 -0000, "Max Bowsher" <maxb@ukf.net> wrote:
> >Patrick Gelin wrote:
> >> When I finish with a local copy of work, how to release it properly. With
> >> CVS it's: cvs release -d path
> >
> >Just delete it.
>
> What happens if I'm using 1.2, and I've locked a file in my working
> copy? OK, so others can --force the lock, but I wonder if there's a
> need for a 'release' equivalent that would release any locks in the
> wc.

I'm assuming that 'svn unlock' from the top of the working copy would
take care of this. But, checking here with the locking implementors
to make sure that is indeed the intention...

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 8 23:18:25 2005