![]() ![]() The Repository Repository Creation Creating a Repository with the Command Line Client Creating The Repository With TortoiseSVN Local Access to the Repository Accessing a Repository on a Network Share Repository Layout Repository Backup Server side hook scripts Checkout Links Accessing the Repository 4. Basic Version-Control Concepts The Repository Versioning Models The Problem of File-Sharing The Lock-Modify-Unlock Solution The Copy-Modify-Merge Solution What does Subversion Do? Subversion in Action Working Copies Repository URLs Revisions How Working Copies Track the Repository Summary 3. ![]() Getting Started Installing TortoiseSVN System requirements Installation Basic Concepts Go for a Test Drive Creating a Repository Importing a Project Checking out a Working Copy Making Changes Adding More Files Viewing the Project History Undoing Changes Moving On. When I converted to SVN from VSS, I decided to go with the copy-merge-modify approach, and then slap locks on everything if it didn't work out well.Table of Contents Preface What is TortoiseSVN? TortoiseSVN's Features License Development TortoiseSVN's History Acknowledgments Reading Guide Terminology used in this document 1. Again, send a message to the mailing list to see if everyone else wants this change. If the 'lock dialog' is a Tortoise thing, you can configure the dialogs to auto-close if there's no errors. In most cases the lock is a manual thing you need to explicitly lock and unlock, so most people using it would want to have to ensure they unlock. Note that the revert functionality does not contact the server, so he might consider that an undesirable change. Stefan is quite good about making fixes, and it sounds like the no-unlock config item should also apply to revert as well as commit. I think your issues are with VisualSVN, you need to contact them to configure the product to not show the dialog and to automatically unlock on revert. How can I resolve these issues? I really don't want to hear a sales pitch on why we should use copy-modify-merge, please just help me resolve the issues. Is there a way to hide this dialog, and only display it if an error occurs. It would be nice to be able to assume that the lock was completed successfully. ![]() Edit: fixed! Everytime I begin to make a change, it automatically gets a lock, but it presents me with a dialog saying "Lock Finished!".Is there any way I can force it to unlock when I revert? When I revert my changes, the lock is not released.Changed TortoiseSVN to auto-close dialogs if no errors.Changed TortoiseSVN settings to not show the lock dialog when locking files.Disable no-unlock to automatically unlock file on commit: no-unlock = false.Added entry to to force needs-lock on all files: * = svn:needs-lock=*.Enabled auto-props in section of config: enable-auto-props = yes.Despite the drawbacks of this model, it is what we are used to, and we want identical behavior from Subversion. Previously, we used Visual SourceSafe, which had the lock-modify-unlock versioning model. I am using the VisualSVN client that integrates into Visual Studio. I have Visual SVN server running on a Windows machine. ![]()
0 Comments
Leave a Reply. |