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

Re: Concurrent versioning = spawn of the devil?

From: Eric <spamsink_at_scoot.netis.com>
Date: 2006-11-08 12:55:59 CET

At 01:38 AM 11/8/2006, Kenneth Porter wrote:

<KP>>>>>Tell us what arguments he uses. Odds are that his opposition stems
from a misunderstanding.<<<<<

He simply says that concurrent versioning is too dangerous, merging is too
difficult and too much subject to error. He says that we are exposing our
clients to too much risk if we subject their code to that kind of an
environment.

It's not helping that we can't see when a file is locked until we try to
check it in. I know ... the answer is "don't lock the damn thing" ... but
that falls on deaf ears, I get "I'm not checking ANYTHING out unless I can
lock it and keep all you jabronis out of it!".

The issues we're having with SmartSVN, mostly the one about SmartSVN
hanging up on us when trying to check in a locked file, are really making
him dig in his heels.

I will have to revisit TortoiseSVN and see if I can get that to work... the
problem there is that it doesn't remember my login name and password and so
I have to enter my password just about every time I change directories,
gets REALLY old after about the third or fourth time. For now we are
trying to do this using login and password rather than SSH public/private
keys, to ease client use, but I guess I'll have to revisit that.

Are there any other GUIs besided SmartSVN and Tortoise? I wasn't able to
find any...

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 8 13:01:45 2006

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