Out of date errors
From: Drs. D.J.W. van Kooten <VanKooten_at_ic2.com>
Date: Mon, 26 Dec 2016 07:44:45 +0100
Dear Ladies and Gentlemen,
I started using Tortoise/Subversion a few years ago but after trying a previous version of a program and after that being unable to roll back to the latest version (I suspect I should have commited first but the program didn't want for it) and losing my changes I keep commiting from time to time but I am not using it as it was intended. When code I use has to be used by one of my employees (who all work on different locations) we simply send files and hand compare, which is a lot safer.
However, despite my "stand alone" use I regularely get out of date errors. The internet is full of this problem with dozens of different solutions. If always costs me a lot of time to solve it. The way I solved it now is to delete the .svn directory and re-register the project.
My question is: why isn't there a simple option to tell the program: stop complaining about conflicts and just commit the whole project/solution in the current state as the right code? Especially the way I work there could not be any out of date or conflict state except a "conflict" caused by the Subversion/Tortoise (no idea which of the 2 caused the problem). I couldn't find something like that in TortoiseSVN-1.9.5.27581 either. That would at least save a lot of time.
Best regards,
Dick van Kooten
IC2 Innovative Computer Consultancy
------------------------------------------------ DISCLAIMER ------------------------------------------------
------------------------------------------------ DISCLAIMER ------------------------------------------------
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
|
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.