I want to stop checkout/update of certain folders in the tree
regardless of where in the tree the update is done, even if they have
already been checked out. I can do this in the access file, and repo-
browser now hides the restricted folders as expected. However they
still get updated/restored by the client. I expected the hidden
folders to be deleted from local copy.
1) Is this expected behaviour?
2) I've also tried to use mod_dontdothat, but I want restricted
folders to be skipped/deleted quietly - not big red error messages
that will scare users!
3) I'd really prefer a server side solution so that special client
software (python ruby perl etc) does not need to be installed, but no
hooks for update unfortunately.
My current solution uses a dos script to perform checkout, but to be
effective the whole repo must be checked out first before applying the
sparse settings (I have tried many other ways believe me). Just feels
a bit klunky to me.
Received on 2012-05-12 13:53:54 CEST