Ronald Cannes wrote:
>
> programmers and designers are complaining about not beeing able to lock
> files. Normally, this is not a problem (we like the edit/merge concept)
> but some files, like uml diagrams and documents in binary format, should
> never be used by more than one person (except read-access, of course.)
For the record, issue 533 ("implement reserved checkouts") and notes/locking-plan.txt (in the source tree) are about this issue.
> What I would REALLY like is a lease based system where person A gets
> exclusive access to a resource for a spesific amount of time, such as 2
> hours or a day. For instance, to obtain exclusive access for 30 minutes,
> I'd like to do a "svn lock <url> -t 30m". Without the "-t" option, the
> exclusiveness would not expire until I commited.
Are you using this "timed" locking in your present version control system?
If so, could you point to on-line documentation for it?
I have not come across this idea before and, to be honest, I can't see how it could work in a useful way, but if I could read about the full syntax (command set) and semantics, that might convince me. For instance...
Why would a user request a time-limited lock when he can more easily request an open-ended lock?
Can the same user issue another "lock -t" to extend his lease time, either before the time has expired, or immediately after it expires?
Does the administrator want to limit the maximum time that can be requested?
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 3 14:22:32 2003