RE: Warning on get lock (Was: Get lock is not visible to other us ers)

Edward Harvey wrote:
> I don't think there's any reason to expect people to only lock files
> that needs-lock.
>
> Users want (on a regular basis) to simply lock a file so nobody else
> will work on it at the same time. Because they don't trust automatic
> merge, and they don't want to merge it manually.

I encountered a great reluctance in my company when we introduced svn: "How
can I prevent others from overwriting my changes", "We will have hundreds of
conflicts" and so on.

Now after working with svn for about two years only new colleagues ask for
locking. The rest has noticed that they don't need it 99.9% of the time and
that none of their resentments has proven true. Some externals who work with
svn here and other version control system at their other customers say that
it's much easier to work with the copy-modify-merge solution.

We set the needs-lock property on non-mergeable files using auto-props.
Occasionally a non-mergeable file slips through our matches, but that's a
two second fix. Admittedly we deal with sourcecode most of the time, so
almost all our files are mergeable.

I think it's mostly a matter of education. I always found locked file a
hindrance because most of the time the colleague didn't need the lock.

Cheers
- Lübbe

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org