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

Issue with locking

From: Oliver <OMatla_at_gmx.net>
Date: 2006-12-18 20:37:45 CET

Hello,

I encountered an issue with detecting locks using TSVN 1.4.1 Build
8219 and Subversion 1.4.3. When locking a file in a repository using
the command line tool, the changed lock status does not show up in
TSVN after updating (the lock owner remains empty). Therefore, the
file can not be unlocked from TSVN anymore - you only have the "Get
lock" option available, not the release option. TSVN does not even
notice the lock if you try to get a new lock on the file - this just
results in an error saying that the file is already locked. Of course,
it is always possible to steal the lock though.

I have not dealt in-depth with the SVN protocol, so I have no idea if
it is possible to get a list of locks from a repository when updating
without having to check each file individually. It would be nice,
however, to know which files are locked before you make changes to the
file, commit and realize that it is locked already. The "SVN lock
owner" column does not make much sense the way it is used now, because
you can only see your own locks, not of the files locked by others...?

Thanks!
Oliver Matla

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Dec 18 20:41:02 2006

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