Hello, ...and a great 2015 to you!
Tortoise is a GREAT tool, it (sort of) saved my life numerous times already. But since years now I've been annoyed by the lack of a few *tiny improvements* that would make Tortoise so much *more productive*. Since I believe many other people must have them on their "wish list" for the next release too, and that adding them should be a matter of an hour or so of an average programmer's time including QC (except perhaps for the archiving below), I decided to share them with you:
- *bulk change of Sync destination*: I have numerous repositories, which I regularly sync among a number of destinations - other machines and backup disks, including portable disks I use for syncing when traveling. All of these numerous Sync destinations are therefore defined for all my repositories. But during a Sync, I spend an inordinate time doing the following:
- open the next repository - switch to the Sync mode - select the Sync destination.That is a /colossal waste of time/... yet one that could be trivially avoided by a "bulk change of Sync destination", namely: - after a change of Sync destination for a repository, ask the user whether they want to apply that same destination as default for all subsequently opened repositories - if so, then - when a new repository is opened in that session, automatically set its default Sync destination to the one defined in the previous step: no need anymore to /once again/ select it in the list of destinations! - *bulk switch to Sync mode*: similar to the above - when I switch to Sync mode, it would be much more efficient to - ask the user whether they want to switch to Sync for subsequently opened repositories - if so, then - when a new repository is opened in that session, automatically switch to the Sync mode - *auto switch to new Sync destination*: when I create & save a new Sync destination, it is obviously /always /because I want to Sync with it - but the Sync destination remains unchanged and I have to explicitly select it! It should automatically switch to the one just created - *archiving* of old versions (this may be a bit trickier to do, I do admit): I'm very regularly (say twice a day) backing my files to at least two external disks in order to make sure no part of my developments could be lost to a disk failure. To do so, I use a backup program of my own concoction that not only only copies changed files, but also /keeps the old version/ of them - you may see it as a very rudimentary CVS. Yet Tortoise itself keeps all the previous versions of a file in a single file that /grows with each change/ (obviously). Consequently, by keeping the previous versions of Tortoise's repositories, I am actually (and implicitly) creating the backup of the same old version of each file with each update of its repository. Obviously, this consumes huge amounts of backup disk space - it would be great to have the possibility to /archive/ old versions of a repository, which would put them into an archive file that would obviously /not cha//nge/ with subsequent updates... and would therefore need to be backed up /just once - not //again and again/ with each update of the repository. The tricky part here is obviously to nevertheless make those old versions available for eventual revert - I do believe it is possible to "forget" old versions, but archiving them without losing them from the version control is different.
Any chance of seeing the above improvements in 2015? Many thanks in advance! Emanuel
------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
