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

Re: Questions about using subversion for non-coding projects.

From: Branko Čibej <brane_at_xbc.nu>
Date: 2005-08-26 00:41:08 CEST

Darren L wrote:

>This was a topic that came up recently, and I recommended the same
>thing for a coworker - the TortoiseSVN plugin works amazingly well,
>but the only complaint was that locking a file does not show up
>immediately in other people's repositories (I believe that this was by
>design, as it's built for offline use). The problem was that locking
>a binary file left the possibility of two users working on the same
>file without knowledge that theother was making changes.
You can mostly avoid this problem by setting the svn:needs-lock property
on such files. If it sees that property, the client will make the file
read-only on checkout or update (unluess you're holding the lock) --
regardless of whether it's locked in the repository or not.

Then, when you try to lock the file to make it writable, there's a
lookup on the server to see if the file is locked.

-- Brane

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 26 00:42:58 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.