Re: preventing commits (this is *not* a classic hook question)

On Mon, Mar 19, 2012 at 4:06 PM, Michael Hüttermann
<michael_at_huettermann.net> wrote:
> Hello,
>
> I'm wondering if there is any strategy for temporary preventing people
> from committing to a svn repository, without the person who sets the hook
> (or sth similar) being the admin of the svn repository. Thus, in this
> case, there is no option to directly access the /hooks/ folder.
>
> A "poor man's" option could be working with locks. But, recursively
> locking a large repo path could be inefficient, and locks can be stolen
> anyway. So it looks like the wrong approach from many perspectives.
>
> Any idea for preventing commits, for a specific time, without being able
> to directly accessing the hooks folder?

The hook script is a program that can access any data you want to make
available to it. Maybe you should approach the question from the
other direction. Who do you want to be able to control the setting,
and where can they store something that the hook script can check?

-- 
  Les Mikesell
    lesmikesell_at_gmail.com