Implementing the Lock->Edit->Unlock cycle

2016-09-28 Thread Anton Shepelev
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 accident

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

2016-09-28 Thread Eric Johnson
Hi Anton, On 9/28/16 8:46 AM, Anton Shepelev 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:

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

2016-09-28 Thread Mark Phippard
On Wed, Sep 28, 2016 at 11:46 AM, Anton Shepelev 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 > easi

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

2016-09-28 Thread Stefan Hett
On 9/28/2016 5:46 PM, Anton Shepelev 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. l

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

2016-09-29 Thread Anton Shepelev
Thanks to everybody for their replies. Eric Johnson to Anton Shepelev: >>> 1. lock and update, >>> lest one might accidentally start editing an >>> old version of some file. > >Subversion supports locks. However, it sounds like >they do not work the way you want them to. > >Subvers

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

2016-09-29 Thread Lorenz
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 o

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

2016-09-29 Thread Anton Shepelev
Lorenz to Anton Shepelev: >>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, >>

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

2016-09-29 Thread Eric Johnson
On 9/29/16 4:58 AM, Anton Shepelev wrote: Thanks to everybody for their replies. Eric Johnson to Anton Shepelev: "svn update" is your friend. Just encourage users to do updates before they start editing. Is there no protection against an oblivious users's losing a day's work merely becau

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

2016-09-29 Thread Andreas Krey
On Thu, 29 Sep 2016 14:58:44 +, Anton Shepelev wrote: ... > Is there no protection against an oblivious users's > losing a day's work merely because he forgot to up- > date his working copy, which was obsolete beyond > merging? He will learn it, lucky eddie style. If you plan doing mass

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

2016-09-30 Thread Anton Shepelev
Andreas Krey: >If you plan doing massive work in a module, you >need to talk to the other people working in the >same module anyway, as they would be annoyed if you >locked the file, and they can't do planned work. OK. >Ideally the other people do their commits in small >increments as