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

Re: [TSVN] What overlays do we NEED

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-04-14 18:57:41 CEST

Peter McNab <mcnab_p@melbpc.org.au> wrote on 04/14/2005 12:04:28 PM:

> So if I understand correctly, merge able things like source files will
> stay writable in the WC, as they currently are.

Yes and no. What you describe is the anticipated way to use the feature,
but in the end what matters is whether you chose to set the svn:nees-lock
property on the file, regardless of what type of file it is. The presence
of that property, tells the Subversion WC code to make the file read-only
until you acquire a lock.

> Is that regardless of whether they are locked by someone else and I've
> done an update?

Yes. The read-only flag has nothing to do with whether someone else has a
lock on the file. That info is not even stored in your WC. All that is
stored is whether YOU have a lock. The file will be made read-only
because the svn:needs-lock property has been set. The intent of the
design is that you will then run the Lock option to make the file
writable. Your lock will then fail if someone else has the file locked,
and presumably Stefan will provide a way for you to see who has it locked,
as well as their lock comment. There will likely also be some kind of
ability for you to "steal" the lock. All of this preventable by hooks of

Lock will also fail if your WC file is not the most recent revision of the

> I can only see a productive use for locking on text type files while
> resolving conflicts.

Yes, ideally locking will only be used on unmergeable files or in special
situations. That is why a file can be locked independent of the
svn:needs-lock property. In that scenario, unless you have some kind of
hooks that send emails, other users would not know you had the file locked
unless they either specifically looked, or they tried to commit a change
to the file. If the latter happens, one you release the lock, they can
still update/resolve/commit.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Apr 14 18:58:00 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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