Question on lock behaviour

I have some questions regarding locking, I have not found the answeres
in the locking GUI/implementation docs or release notes, so I'm asking here:

* Does locking depend on the svn:needs-lock property, or is locking
allowed on all files, even if they do not carry the needs-lock property
(giving a "locking is optional" behaviour)? If locking is optional, will
locked files get the read-only attribute on an update if someone else
has locked the file?

* Is it allowed to lock multiple files in one command, like
"svn lock *.bin"?
If yes, is this some kind of an atomic operation, meaning:
- same lock comment used for all files?
- repository lock-hook called once with a file list or once per file?
- no problem with concurrency when two users try the lock the same group
of files at the same time.

* Does locking/unlocking a file without modifying the file require write
access rights (in terms of mod_auth_svn)?

* Is it possible to lock a directory (i.e. with the effect of locking
all files in that directory)?

Maybe someone creates a win32 binary of svn 1.2RC1, then I could try myself.

Thanks!

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 9 11:13:46 2005