> it happened again: Someone *move*d trunk to a branch...
...
I think more verbose dialogs in the repo-browser would be a good thing.
(It's easy to make mistakes when working directly on the repository
where you don't have the luxury of revert.)
I would even go as far as suggesting an extra set of confirm-messages
for all write-operations before you get to the commit-dialog. Something
along the lines of "You are performing an operation directly on the
repository. Please review the changes before committing. (Ok/Cancel)"
It should be possible to disable these extra confirm-messages in the
configurations dialog.
...when I think about it maybe we should add a possible parameter to the
start-commit hook to inform the hook that this commit is being made from
the repo-browser. Hmmm... But that wouldn't really work now as hooks are
linked to WC:s, and not generally to actions...
So: I would suggest adding a default set of hooks, placed in the TSVN
installation folder, that (if there) are called regardless of where the
operation is made. These hooks would get a fixed set of arguments passed
to them, like the path in repository and path to WC (if any) and so on.
These "global" hooks would work analogously to how the hooks work in
server side subversion and a useful extension to per-wc-client-hooks.
I think that would make an excellent addition and prime the
hook-functionality for corporate use, where "global hooks" could be
easily distributable. If special handling is needed for some paths, the
script itself can then contain the logic to find out what it should do.
Hans-Emil
PS. Sven, what you need is a server side hook-script that checks if
someone is moving or deleting trunk, and stops it right there. DS.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Sep 19 09:15:13 2006