RE: Communication of LOCKS and CHANGES

> So it sounds like you want to use the "Lock Communication" mechanism

Actually, I am already familiar with the svn:needs-lock property. It is
useful for its own purposes, but it's not what I'm talking about here.

Regardless of the needs-lock property, it is totally possible for some
user at another location to lock or commit a file. That change will not
be communicated to you automatically, and at present it is impossible
for you to automatically receive that information, no matter what you
try. (Unless you want to use needs-lock on every file, and create the
needs-lock property automatically on all new files and be forced to lock
every file before every edit ... but I think that's overkill.)

What I'm talking about here is to create the ability, if you want it, to
let this information be communicated to you automatically. If you don't
want to use this ability, you don't use it and that's ok too.

The needs-lock solution is already pretty well implemented, in my
opinion. I'm trying to talk about a solution to a different problem -

The problem at hand is: There is no possibility (presently) to
automatically communicate somebody else's changes or locks. You have to
check manually. I believe this is a useful feature that can be
implemented without harming anything else.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 21 16:37:12 2007