Thank you. I see that I edited out my comment that I'm an infrequent user of Tortoise. I did indeed read those Chapters several times 1 and 2 years ago. Sadly, I'm not one of the lucky ones who can store two rarely-used chapters forever.
There have been many bug fixes to Tortoise. This dedication is *very* much appreciated, but it also means the chances of encountering bugs were once higher and the manual wasn't written for those cases. I've had situations where "Clean up" and "Resolve" didn't. As you take more and more drastic steps to work around the problem, you can eventually divorce your code completely from SVN and "Update" will not work without blowing away your latest code. So you back up, blow away, and paste - it only takes time.
Choices quickly get set in stone so it's important they're sound; I think some of SVN's were counter-intuitive. If the money to pay expensive programmers was coming from your own pocket, would you be satisfied with tools that take time away from finishing your deliverable? (Would a programmer who only needed to be expert at C be less expensive than one who also had to know the vagaries of various ancillary tools?) More-intuitive software is always a good thing and it seems a waste that Tortoise's menus couldn't put their abundant white space to better use. Many applications allow for internationalization; perhaps the same approach could be used to allow the user to enhance the menus?
It's easy to kill suggestions. Isn't that how SVN came to be?
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-12-07 07:52:14 CET