Maciej Miąsik wrote:
> In our project we are using Subversion and TortoiseSVN to manage all of
> our binary assets. For that reason we are using lock/unlock feature to
> prevent users from simultaneously editing the same unmergeable files.
> Unfortunately, many of those users are artists who still perceive the
> Subversion more like a nuisance rather then the extremely useful thing
> it really is.
> They usually forget about updating their working directory before they
> start working on a file or forget to commit files after changes have
> been made. But they remember that the file has to locked before editing
> and unlocked when the work is done. For that reason I hard coded the
> additional functionality in our TortoiseSVN - "update before lock" and
> "commit after unlock", which prevents from the most of possible conflicts.
> I thought it would be beneficial for other TortoiseSVN users to have
> such functionality available and I would like to file "official" request
> for implementing it. Of course it should be only activated with
> appropriate checkboxes in Settings screen.
I think not. Update before lock is dangerous because the simple act of
acquiring a lock can make changes in your working copy without you
realizing it. Someone else requested this only 2-3 days ago and it was
refused for that reason.
Why would we want "Commit after unlock" when we already have "Unlock
after commit"? Apart from being the wrong order for doing things, there
seems no reason to believe that unlocking is more intuitive than committing.
I think what you really need, if you have un-cooperative users, is a
simple program of your own which has the minimal feature set, worded in
terms that your users understand. You can use TSVN's command line
interface to call the various dialogs from your own program.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Oct 21 11:53:24 2005