My team recently had a server-side hook installed to prevent locking
an artifact on one branch if it is already locked on another branch,
or on trunk. The intent is to allow us to branch hard-to-merge files
with "svn:needs-lock" set and not worry about other people editing it
on other branches.
This gets us pretty close, but now we need to remember NOT to release
our lock during commits to the branch, until we finally merge back to
trunk. I'd like to make this the default behavior. I found the
"no-unlock" setting in the Subversion config file, but if I leave it
at "yes" then it would be too easy to forget to release the locks
after we merge to trunk. So, I want to make this change based on where
the working copy is pointing.
I created a .bat file to modify %APPDATA%\Subversion\config to toggle
the miscellany/no-unlock setting on and off depending on whether "svn
info" shows the WC pointing to somewhere under "branches" or not. The
script works, I verify it modifes the config file as intended. If I
run the script manually, then bring up the commit dialog with TSVN,
the "keep locks" button reflects the modified setting in the config
But, if I try configuring the .bat file as a client-side "start
commit" hook, even though I can verify that the script runs, and the
config file gets modified, the "keep locks" checkbox does NOT get
updated with the new value. It keeps the previous value. I thought
this would work, because "start commit" runs before the dialog is
Does the hook script run too late to affect the checkbox default
state? Is there some other way I can accomplish setting default state
of this button depending on WC path?
I'm using 1.7.12, so I configured the hook script through the
"settings" dialog, not via tsvn: property as in 1.8.x.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-06 22:50:53 CEST