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

Re: Feature request : locking : which working copy

From: Steve Williams <stevewilliams_at_kromestudios.com>
Date: 2006-06-19 12:54:59 CEST

Gal Aviel wrote:
> Working with Novice users, they tend to checkout several working copies, then
> then don't remember from which working copy they locked a file, and then lock
> has to be broken.
> Having this piece of information in the repository would be helpful to determine
> which working copy holds the lock token, so that it can be cleanly unlocked.
> Opinions ? should I submit as a feature request / enhancement ?

There is a major flaw in your plan. A user can move a working copy.
The server therefore does not, and should not, know anything about a
particular user's working copy.

I would suggest a large piece of wood as a management tool.

This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 19 12:56:58 2006

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

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