Hi,
I'm not a subscriber of the TortoiseSVN mailing list, so please reply directly
to eeprom@bol.com.br
I'm using Subversion 1.2.0 rc2 and the 'pre-lock' and 'pre-unlock' hook
scripts to control locking/unlocking. And I'm using the needs-lock auto-props
option in my user configurations with TortoiseSVN.
Problem 1: When commiting a locked file, Subversion's default behaviour is to
keep the lock. So if the "Keep Locks" option is NOT marked at TortoiseSNV's
commiting dialog, TortoiseSVN should remove the lock, but it doesn't. The
file is still locked but TortoiseSVN seems to *think* it isn't and changes
the overlay into a 'lock' (meaning not-locked) and sets permission to
read-only.
Problem 2: If the "Keep Locks" IS marked at TortoiseSNV's commiting dialog,
the overlay icon of that locked file changes back into a 'lock' anyway and
permission is set to read-only (it should become a green 'correct' sign
meaning commited, and STAY read-write meaning locked for me).
Thanks for this great software :-)
eeprom
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu May 5 08:24:58 2005