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

Wrong behaviour of svn unlock?

From: Weiss Gerd <gerd.weiss_at_evosoft.com>
Date: 2005-12-14 11:30:18 CET

I have a small problem with the behaviour of svn unlock.

The manual says:
Unlock each TARGET. If any TARGET is either locked by another user or no
valid lock token exists in the working copy, print a warning and
continue unlocking the rest of the TARGETs. Use --force to break a lock
belonging to another user or working copy.

When I use svn status --show-updates ./ in the root of my working copy I
get following output:

     K 1049 Desktop/test.txt
     O 1049 test.txt

Now, when I execute: svn unlock ./test.txt command ./Desktop/test.txt
I thought, I get a warning, that "Desktop/test.txt" could not unlocked
and then "test.txt" will be unlocked. But I just get the warning and
nothing else happen.
After this command svn status has the same output as before.

Is this a bug in the command, or an mistake in the manual, or something

I use Subversion 1.2.3 on an RHEL4 with Apache 2.0.52-19.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 14 20:26:34 2005

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