update/lock and unlock/commit – another approach

I would like to return to my previous feature suggestion which had an
intention to reduce the possibility of conflicts between different
versions of unmergeable digital files. I understand that "forced" update
before lock isn't the greatest idea, although it works for my users. I
would like to propose another solution.

Let's suppose that before locking a file TSVN first (if the appropriate
option is enabled) checks the status of the files it is about to lock.
If the server holds the newer version of that file TSVN displays the
following message box:

"The server hold the modified version of file which is about to be
locked. Do you want to update the file before lock?"

with UPDATE and IGNORE buttons.

When the user presses UPDATE the file is updated and then locked, if
IGNORE is chosen everything works as it works now.

Similar check could be done while a file is being unlocked. If the file
had been modified the message would be:

"The unlocked files has been modified. Do you want to commit it to the
repository?"

again with COMMIT and IGNORE buttons.

Or something like that. What do you think about such feature?

-- 
Maciej MiÄ…sik, Design Manager, CD Projekt RED
Email: maciej.miasik@cdprojekt.com
Web: www.TheWitcher.com
"The Witcher looks to be a unique action game with an unprecedented
number of paths for a game of this type, along with an intriguing
and harshly beautiful game world to explore." - RPG Dot
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
--