Re: Implementing the Lock->Edit->Unlock cycle

On Wed, Sep 28, 2016 at 11:46 AM, Anton Shepelev <anton.txt_at_gmail.com>
wrote:

> Hello, all
>
> We are migrating to SVN from the dreaded SourceSafe
> and should like to retain, if only at the start, the
> exclusive check-out process, with the following
> *atomic* operations which should be performed as
> easily as possible:
>
> 1. lock and update,
> lest one might accidentally start editing an
> old version of some file.
>
> 2. commit and unlock.
>
> Can SVN be configured to have such operations, and
> how?
>

See these sections of the book:

http://svnbook.red-bean.com/en/1.7/svn.basic.version-control-basics.html#svn.basic.vsn-models
http://svnbook.red-bean.com/en/1.7/svn.advanced.locking.html

and particularly this section:

http://svnbook.red-bean.com/en/1.7/svn.advanced.locking.html#svn.advanced.locking.lock-communication

Locking a file will not force an update to happen, but the lock itself is
not held on any specific revision either.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/