On 5/2/07 2:13 PM, "Andreas Hasenack" <andreas@conectiva.com.br> wrote:
> I would like to be able to do something like "svn lock" for a whole
> directory, and not just for a file. Using it for all files in the
> directory is also not practical for me.
Why not? I assume you're wrapping your commands. If you get the list of
directory files, you can just do one big 'svn lock file-list' and it will
lock them all at once.
>
> Most possibilities I thought of use some sort of signal and a hook to
> detect that signal. For example:
> - use svn lock on a particular file and have a pre-commit hook detect it
> and deny the commit for anything under the directory
> - use svn properties. Initially I liked this a lot, because I could
> invent my own property and also because they can attach to
> directories. But the properties are versioned. So the history would
> have a lot of locks/unlocks. I'm not sure I want that.
> - dynamic ACL change. In other words, have another layer of ACL in
> addition to what I'm currently using (svnperms.py). Probably two
> different calls to svnperms.py in pre-commit, using different
> configuration files that would be changed by other means.
>
> This lock need not to be mandatory, i.e., it would suffice for the user
> doing a commit to know it was locked. But I wouldn't mind it being
> mandatory.
>
> Suggestions? Comments?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 2 22:44:56 2007