Hi guys, nice work on the Tortoise interface. It works quite well.
I have a suggestion that would make Tortoise easier to use in a wide-geography usage model. We have a subversion server set up in Israel, and have a number of (one-way) mirrored sites around the world, including a mirror in Oregon where I am. It is much faster for me to check out and update code, view the log and other read-only type activities if I reference the server at my local site; but commits must be done directly to the the main server in Israel. I can switch between the two archives manually, but this is rather tedious.
It would be great to have a option where Tortoise could have separate update-from and commit-to urls. If this option were selected, updates would automatically come from the (near-and-fast) update-from server, as well as blame searches, diffs and all the read-only activities. Commits would automatically go to the (far-away-and-slow) commit-to server. Since there is somewhat of a time delay between mirror operations, even if I did an update from the mirror, there could be very fresh changes on the master site that had not yet been mirrored, so the commit function would probably have to do several things: switch to the commit-to server, check to see if an update is required, notify user & ask whether update only/update & commit/cancel, then update from commit-to server, commit, and switch back to the update-from server as requested.
Does this sound feasible and/or useful to anyone else?
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-01-12 07:55:23 CET