On Thu, Aug 8, 2013 at 12:34 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 06.08.2013 22:50, Ben Fritz wrote:
>> 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.
> The dialog isn't shown yet, but it is already initialized. Only the
> status of all files isn't fetched yet so you can only change the files
> in that hook script. Everything else is not changeable by the hook script.
Thanks, that's kind of what I figured when it didn't work.
> I don't think it's possible to achieve what you want with a hook script.
> Or any other way I can think of, sorry.
The best I came up with was to install it as a post-update hook instead.
Best practice would have us do an svn update before any commit
(sometimes you NEED to), and if you're just working a single branch
then the initial checkout or switch will also run the script.
I'm considering a server-side hook update to automatically create a
trunk lock instead of requiring users to remember to keep their branch
locks after commit; but that comes with its own set of troubles
(mainly, not having a working copy for that trunk lock). It would have
the advantage of not requiring everybody to configure a client hook.
Thanks for your reply.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-08 20:04:00 CEST