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

Re: Finding Locks

From: Rainer Sokoll <R.Sokoll_at_intershop.de>
Date: 2007-09-17 17:32:17 CEST

On Mon, Sep 17, 2007 at 11:19:45AM -0400, Bicking, David (HHoldings, IT) wrote:

> Interesting. What happens when a person gets a lock on a file while
> another person begins working on his own local copy? Am I correct in
> believing that the user who doesn't have the lock will do his work
> oblivious to the new lock until he attempts to commit? What happens if
> the person who has the lock made changes that make the second person's
> work totally useless?

If the file has the property svn:needs-lock, the file is r/o in the wc's
filesystem. That means, without having a lock, it is (not so easy) to
edit the file.

> It seems to me that it would be useful to know this with a quick
> "update" operation. Keep in mind that I'm looking at this through the
> eyes of joe (microsoft) developer who is using an IDE integration. Many
> of them are a bit more "lazy" when it comes to SCM. They don't want to
> execute a "list all changes on the server" operation. They want to see
> a visual notification that something interesting changed ("oh, gee, with
> this update, the file I'm editing suddenly has a padlock on it! I
> wonder who did that?").

TSVN has its own overlay icons, it is easy to see which files are r/o
and for wich files the user has a lock.
The same for Subclipse, others I do not know.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 17 17:28:51 2007

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.