RE: Re: Feature / Bug - File lock icon, checking for modifications
From: Peter Yamamoto <yamamotop_at_page44.com>
Date: 2006-04-25 21:22:35 CEST
As well:
Now all of a sudden, these users know something I would give a left arm for in project management!-)
The file lock mechanism should be adequate. It simply means that the user will recognize an unmergeable file before attempting to modify it and hence at that point can check for the lock and lock it. As Stefan points out on one hand you say the users have this management problem, but on the other hand you say they are perfectly willing to look at an icon before editing... I somehow doubt it (and in any case this still isn't reliable regardless unless the person himself actually asks for the lock and gets it).
That is the safest way to enforce this it seems and it's a modest overhead for the danger it protects against. This hardly seems like extra work... If you want to avoid that step then this sounds like a job for scripting in the apps they are using to modify the files (some of which do support this type of behavior, eg built in version control hooks).
Peter
Edward Harvey wrote:
> There's no way any one of those people wants to remember all the files
If they don't want to check a file before they start modifying it, then they also don't look at the overlay that file has. So what's your point here?
Stefan
-- ___ oo // \\ "De Chelonian Mobile" (_,\/ \_/ \ TortoiseSVN \ \_/_\_/> The coolest Interface to (Sub)Version Control /_/ \_\ http://tortoisesvn.tigris.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org For additional commands, e-mail: users-help@tortoisesvn.tigris.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org For additional commands, e-mail: users-help@tortoisesvn.tigris.orgReceived on Tue Apr 25 21:22:41 2006 |
This is an archived mail posted to the TortoiseSVN Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.