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

Re: Locking functional spec: branches

From: Branko Čibej <brane_at_xbc.nu>
Date: 2004-10-15 01:37:27 CEST

Michael Brouwer wrote:

> Something that strikes me as a limitation of the current locking spec
> is that it is limited to wc's only.
> I like to think of a wc as a special case of a branch that hasn't made
> it into the repository yet. If for some reason you want to move your
> wc from one machine to another, an easy way to do this is to make a
> branch for the change you are working on. commit your partially
> completed work and checkout the branch in the new location.
> IMHO it should be possible to have a branch (rather than a particular
> wc) own the lock on a file (probably limited to the version of the
> file that the branch contains direct copies of).

A lock cannot be owned by an object in the repository, it has to be
owned by a principal. In fact locks are not owned by WCs, but by users.
It is reasonable to allow a user to remove their WC, fly to melbourne,
checkout again and use the lock discovery mechanism to retrieve their
lock tokens.

-- Brane

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 15 01:37:42 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.