subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benjamin Fritz <fritzophre...@gmail.com>
Subject Re: Managing "needs-lock" files on multiple branches
Date Thu, 13 Jun 2013 20:05:28 GMT
On Thu, Jun 13, 2013 at 2:47 PM, Mark Phippard <markphip@gmail.com> wrote:
>
> The hook is running on the server, so it could access the repository
> via file:// URL to do the lock.  This does not require authentication.
>

I DID NOT KNOW THIS! Is that documented somewhere? This should allow
my pre-lock hook to work exactly as I wanted! What other svn commands
that also behave this way?

> In SVN 1.8, the svnadmin command can be used as well:
>
> $ svnadmin help lock
> lock: usage: svnadmin lock REPOS_PATH PATH USERNAME COMMENT-FILE [TOKEN]
>

I don't know what version of SVN is running on our server, but I know
it is definitely less than 1.8, sadly.

> Use --bypass-hooks to avoid
> triggering the pre-lock and post-lock hook scripts.
>
> Valid options:
>   --bypass-hooks           : bypass the repository hook system
>

I've made sure the pre-lock hook will succeed under normal
circumstances (i.e. file is not locked, or --force was passed) if the
file is NOT on a branch. So a recursive call to lock a file NOT on a
branch shouldn't be a problem, right?

Mime
View raw message