[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Lorenz <lorenznl_at_yahoo.com>
Date: Thu, 29 Sep 2016 13:50:00 +0000

Anton Shepelev wrote:
>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.
>[...]

"svn lock" will fail if your working copy is not up to date.

So using svn:needs-lock and an editor that prevents you from modifying
read-only files should do the job.

-- 
Lorenz
Received on 2016-09-29 15:53:43 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.