Working Copy in Inconsistent State

You know, for an atomic SCM, subversion sure as hell seems to leave my
working directories screwed up a little too often:

svn: Invalid change ordering: new node revision ID without delete.

Well - I sure as hell typed the commands in the right order, it's not too
hard: svn mv a b.

How many other people have had to check out a new working copy and copy
changes over and commit because their working copy was broken _again_
without any explanation provided and a cryptic error message that doesn't
really explain what the problem actualy is?

Is there any hope that Subversion will improve on the current state of
affairs or should we all be looking to shell out for a commercial scm that
works more often?

Alex.
Received on Mon Jul 31 03:03:05 2006