Behaviour of lock-synchronisation when switching a working copy.

In issue 2680, something is called a bug, which I doubt it really is.
In an attempt to clear 1.5-consider issues, I'm trying to establish
whether the issue should be rescheduled or closed as INVALID.

The issue is:

- Create a working copy of branch A
- Lock a file in A (say foo)
- Switch to branch B
- Switch back to branch A

Now you'll observe the working copy lost the lock.

maxb and I think in this scenario of 'switch' as a new checkout, only
more efficient. Which means switching back to A in step 4 is acting as
expected. In other words we think of the issue as INVALID.

sussman on the other hand says that switch isn't anything other than
an update. If you look at it that way, how should an update from a
non-locked resource to a locked one behave? Even though the user
himself holds the lock, should it be automatically re-acquired? How is
the working copy supposed to know?

bye,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 20 19:13:50 2007