Re: how to disable svn's copy and move command?

[Nico Kadel-Garcia <nk...@gmail.com>]

On Thu, Dec 1, 2011 at 6:23 PM, David Brodbeck <br...@uw.edu> wrote:
>
>
> On Thu, Dec 1, 2011 at 3:01 AM, zhiwei chen <zh...@gmail.com> wrote:
>>
>> hi,all.
>>
>> I use webdav to host a svn repository, for some reason I want to
>> disable copy and move command, ie. uses can't use 'svn copy' and 'svn
>> move' to commit.
>>
>> I know I can use pre-commit to disable copy and move, and is there
>> another way to do this?
>
>
> I'm not sure this will accomplish what you want.  It won't prevent users
> from checking out files, using their system's own filesystem commands to
> move them, then checking them in in a new location.

I can actually see reasons for this. Forcing an import forces a new
history to be started, and breaks the cross-branch dependencies that
are the sworn archenemy of clearing out debris with svndumpfilter when
rebuilding or transferring a repository.

Re: how to disable svn's copy and move command?

[Les Mikesell <le...@gmail.com>]

On Wed, Jan 18, 2012 at 6:14 AM, Nico Kadel-Garcia <nk...@gmail.com> wrote:
>>>
>>> hi,all.
>>>
>>> I use webdav to host a svn repository, for some reason I want to
>>> disable copy and move command, ie. uses can't use 'svn copy' and 'svn
>>> move' to commit.
>>>
>>> I know I can use pre-commit to disable copy and move, and is there
>>> another way to do this?
>>
>>
>> I'm not sure this will accomplish what you want.  It won't prevent users
>> from checking out files, using their system's own filesystem commands to
>> move them, then checking them in in a new location.
>
> I can actually see reasons for this. Forcing an import forces a new
> history to be started, and breaks the cross-branch dependencies that
> are the sworn archenemy of clearing out debris with svndumpfilter when
> rebuilding or transferring a repository.

The pre-commit hook should work, but it will prevent the
normal/expected use of branching, tagging etc., so it isn't going to
act much like a subversion repository when you break those operations.

-- 
   Les Mikesell
      lesmikesell@gmail.com