Eric Ahlstrom wrote on Fri, Apr 01, 2016 at 04:38:06 -0600:
> I appreciate all input on my rfi, we are specifically asking for input from
> Solidworks users with experience using svn as their basis pdm.
Changed the subject to draw their attention. (SolidWorks users: see
Eric's first post in the t
I appreciate all input on my rfi, we are specifically asking for input from
Solidworks users with experience using svn as their basis pdm.
On Apr 1, 2016 2:22 AM, "Johan Corveleyn" wrote:
> On Fri, Apr 1, 2016 at 9:32 AM, Stefan Sperling wrote:
> > On Fri, Apr 01, 2016 at 05:36:34AM +, Danie
Branko ?ibej wrote:
>On 01.04.2016 10:21, Johan Corveleyn wrote:
>> On Fri, Apr 1, 2016 at 9:32 AM, Stefan Sperling wrote:
>>> On Fri, Apr 01, 2016 at 05:36:34AM +, Daniel Shahaf wrote:
Normally, 'svn mv' does two things: (a) rename the file on disk,
(b) record in .svn/ that the rena
On 01.04.2016 10:21, Johan Corveleyn wrote:
> On Fri, Apr 1, 2016 at 9:32 AM, Stefan Sperling wrote:
>> On Fri, Apr 01, 2016 at 05:36:34AM +, Daniel Shahaf wrote:
>>> Normally, 'svn mv' does two things: (a) rename the file on disk,
>>> (b) record in .svn/ that the rename had happened. As of 1
On Fri, Apr 1, 2016 at 9:32 AM, Stefan Sperling wrote:
> On Fri, Apr 01, 2016 at 05:36:34AM +, Daniel Shahaf wrote:
>> Normally, 'svn mv' does two things: (a) rename the file on disk,
>> (b) record in .svn/ that the rename had happened. As of 1.8, we allow
>> the user to tell 'svn mv' to do o
On Fri, Apr 01, 2016 at 05:36:34AM +, Daniel Shahaf wrote:
> Normally, 'svn mv' does two things: (a) rename the file on disk,
> (b) record in .svn/ that the rename had happened. As of 1.8, we allow
> the user to tell 'svn mv' to do only (b). We don't expose that ability
> in the standard comm
Eric Ahlstrom wrote on Tue, Mar 29, 2016 at 11:53:03 -0600:
> renaming/reorganizing files requires incredibly complex work arounds.
What workaround? Do you refer to the need to call 'svn mv' to tell svn
about the rename?
Normally, 'svn mv' does two things: (a) rename the file on disk,
(b) record
On Tue, Mar 29, 2016 at 1:53 PM, Eric Ahlstrom
wrote:
> To whom it may concern,
>
> Sorry, I'm not a software developer so this message is not following the
> protocol for reporting bugs. Our company primarily deals with aircraft
> electronics integration. Software is a small part of our operati
[mailto:eric.ahlst...@borsight.com]
Sent: Tuesday, March 29, 2016 12:53 PM
To: users@subversion.apache.org
Subject: SVN compatibility question
To whom it may concern,
Sorry, I'm not a software developer so this message is not following the
protocol for reporting bugs. Our company primarily
That's an interesting problem you describe. I'm not familiar with
SolidWorks, but you provide enough information to take some guesses.
Subversion uses an "optimistic lock" design approach which might trigger
some of the problems you're seeing. You say you wish to "prevent" users
from editing the s
To whom it may concern,
Sorry, I'm not a software developer so this message is not following the
protocol for reporting bugs. Our company primarily deals with aircraft
electronics integration. Software is a small part of our operations and
our people have used Tortoise SVN successfully for years
11 matches
Mail list logo
