* Your local working copy is trashed, so just make a new one and see if that's any better. Regular problem, usually the "throw it away and start again" approach is the most effective. * It not being Mercurial. * Tortoise. Check if command-line svn client likes it any better * Tortoise being generally cack and evil * Today's Tortoise process having barfed, so whacking the process and just restarting might help. * Tortoise fighting over versions with SVN (usually bignum, but there have been smallnum issues at times. * Tortoise silently up-versioning your LWC (bastard!, Smeagol hates it he does, especially when it's happening gradually across a whole office) and SVN client then failing to know how to work it.
Tortoise is a bit shit really. Then 90% of the problems I ever have with svn are people using crap graphical clients. People just look at me pained when I suggest they just type it in on the command line.
Given I never branch code mercurial seems identical apart from requiring twice as much typing. :-)
I spent yesterday cursing subversion too. My clients all seem to hang, and if I try the command line it refuses to work because the clients have upgraded the working copy with metadata which is too recent, and if I switch clients then they don't work with another subversion repo I need to connect to, and .... ugh.
And if I need to move files I need to delete them and recreate them and lose all my change history because it's too rubbish to have the notion of file moves and ... stupid system.
Ah, true. Whenever I'd googled for it before the answer that had come up was 'try svn add followed by svn delete!' which was not exactly what I'd hoped for.
And the clients I've used don't have the support for it either - which is an issue with the clients, not the system, but then at some point you need decent clients. I'll do many things on the command line, but 'svn add' for complicated project structures with lots of generated resources isn't one of them.
Comments 14
* Your local working copy is trashed, so just make a new one and see if that's any better. Regular problem, usually the "throw it away and start again" approach is the most effective.
* It not being Mercurial.
* Tortoise. Check if command-line svn client likes it any better
* Tortoise being generally cack and evil
* Today's Tortoise process having barfed, so whacking the process and just restarting might help.
* Tortoise fighting over versions with SVN (usually bignum, but there have been smallnum issues at times.
* Tortoise silently up-versioning your LWC (bastard!, Smeagol hates it he does, especially when it's happening gradually across a whole office) and SVN client then failing to know how to work it.
Reply
Given I never branch code mercurial seems identical apart from requiring twice as much typing. :-)
Reply
Reply
Reply
Reply
And if I need to move files I need to delete them and recreate them and lose all my change history because it's too rubbish to have the notion of file moves and ... stupid system.
Reply
svn mv oldfile newfile
(Unless you're moving them between repositiories).
Reply
And the clients I've used don't have the support for it either - which is an issue with the clients, not the system, but then at some point you need decent clients. I'll do many things on the command line, but 'svn add' for complicated project structures with lots of generated resources isn't one of them.
Reply
That's what command line tools like find and xargs are for. I'd certainly trust those more than an automated tool.
Reply
Leave a comment