[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Lock working copy and prevent accidental update

From: Tomislav Kimovski <tkimovski_at_hotmail.com>
Date: Mon, 20 Mar 2017 19:51:47 -0700 (PDT)

I think it would be very beneficial to have the ability to lock the working copy and prevent accidental update from the repository.

I have both staging and production instances (working copies) of the project on the production server. The staging instance sometimes needs several updates in a day before updating the production instance. It's easy to confuse the two and mistakenly update the production instance when the staging was intended. Since the production instance needs updating from the repository once in a while, it would be beneficial if it could be locked (context menu item?) and report an error when update is requested.

I'm not overly familiar with TortoiseSVN, so there is a chance that there is such a feature or perhaps my setup is not ideal. Any feedback would be highly appreciated.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2017-03-21 03:52:01 CET

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.