Re: Communication of LOCKS and CHANGES

Bicking, David (HHoldings, IT) wrote:

> Given the above it makes sense that:
> ====================================
> 1. A developer who wants to make a change to a file might have to do
> extra work if he makes those changes, attempts to commit, and finds the
> file is locked. Why? If the locked file is later committed and
> completely altered from his base copy, the merge effort is especially
> painful.
> 2. Said developer has no reason to specifically look for locks, since
> the normal modus operandi is to edit, merge, and commit.

I'm missing something here. If you are working with content that can't
be merged, why is it normal operating procedure to do the work without
obtaining a lock? Or in the problem case, why do only some people know
to obtain the lock even though other people are working on the same
file? Note that if it really is standard procedure not to lock, there
won't be any locks for you to see anyway...

-- 
   Les Mikesell
    lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org