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
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
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,
>>
(Not subscribed, please CC me on answers. Thanks!)
Hello,
I suspect this is a user problem somewhere, but since I upgraded to
Ubuntu 16.10 (Subversion 1.9.4 versus 1.9.3 in 16.04) svn has stopped
using GPG-Agent and started using GNOME Keyring to store my password.
As a test, I deleted all G
Daniel Shahaf wrote:
>Nico Kadel-Garcia wrote on Tue, Sep 27, 2016 at 19:44:07 -0400:
>> If you switch the upstream repo for a software source repo, recompile.
>> It's the best way to make sure you've not left some datestamped file
>> inconsistencies that could mess with the system.
>
>Subversion s
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
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
