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

Re: svn up --paranoid [was "Disabling automatic conflict resolution" ]

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-08-18 23:55:58 CEST

"Walter Nicholls" <walter.nicholls@cornerstone.co.nz> writes:

> Or am I missing something? I know there is a religious war in here (RCS
> locking vs CVS merging), but we do a lot of Visual Foxpro development,
> and it makes heavy use of binary-format files. It is very important to
> prevent multiple checkouts of a VCX (visual class library) file for
> example and CVS/SVN provides no easy way to do this that I can see.

There's been a lot of discussion about ways in which svn can someday
implement an 'advisory locking' system (as a way to facilitate
communication between developers), or even a 'true' locking system, as
the WebDAV spec suggests. In fact, a large group of us wrote up
design ideas at the last apachecon, and put them into
notes/locking-plan.txt. But it's not trivial at all.

CVS has a 'watch/edit' facility, to aid communication. You probably
want that. SVN has no such thing yet.

As a matter of religious war -- well, ye, if you read the beginning of
chapter2 in svnbook.red-bean.com, you'll see how most svn developers
feel whenever somebody says "but I *must* have locking!" :-)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 19 00:00:40 2003

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