Re: Feature suggestion: update/lock and unlock/commit
On 10/21/05, Maciej Miąsik <Maciej.Miasik@cdprojekt.com> 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.
Can you send us a patch with your changes? If you also could add the
option in the settings dialog for that, that would be great!
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
Received on Fri Oct 21 11:43:25 2005
This is an archived mail posted to the TortoiseSVN Users