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

Consider Lock Required for SVN Move

From: photoTed <tmead_at_generalcode.com>
Date: Wed, 3 Jun 2009 07:17:13 -0700 (PDT)

We are deploying SVN as a content management replacement for Documentum. As
such it is being used by less tech savy users. We are implementing the
svn:needs-lock property to reduce the possibility of these users creating
conflicts. That is working well.

SVN Move is a chink in that armor. User A moves (happens to be with
Tortoise, but that is just the client, not the underlying architecture) a
file to a different folder. As it does not have to be locked, if the user
does not check the file in, User B can still open the file from the original
folder without knowledge that user A moved the file. Eventually everything
can be sorted out, but if the SVN Move operation of an object with
svn:needs-lock property required the lock, the second user would not be able
to obtain his/her lock on that object until the User A committed the move

Architecturally requiring that, seems consistent with the concept of a lock.

Thanks for your consideration.

Ted Mead

View this message in context: http://www.nabble.com/Consider-Lock-Required-for-SVN-Move-tp23852307p23852307.html
Sent from the Subversion Users mailing list archive at Nabble.com.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-03 16:25:54 CEST

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