api_ref_data $ svn status aggtests/test/xml/xpath/ # OK, svn says there's nothing there. Let's put something there api_ref_data $ mv pips3.t !$ mv pips3.t aggtests/test/xml/xpath/ # Yup. svn say's it is not in the repository api_ref_data $ svn status aggtests/test/xml/xpath/ ? aggtests/test/xml/xpath/pips3.t api_ref_data $ svn add aggtests/test/xml/xpath/pips3.t A aggtests/test/xml/xpath/pips3.t # OK, added just fine. Let's commit it. api_ref_data $ svn commit !$ svn commit aggtests/test/xml/xpath/pips3.t Adding aggtests/test/xml/xpath/pips3.t svn: Commit failed (details follow): svn: File '/svn/pips3/branches/api_ref_data/aggtests/test/xml/xpath/pips3.t' already exists svn: Your commit message was left in a temporary file: svn: '/home/poec01/source/pips3/branches/api_ref_data/aggtests/test/xml/xpath/svn-commit.tmp'
Yup. Subversion said it wasn't in my repository. I had to do a svn rm directly to the repository. That sucks.
# Yup. svn say's it is not in the repository
api_ref_data $ svn status aggtests/test/xml/xpath/
? aggtests/test/xml/xpath/pips3.t
Your comment doesn't match the code
"svn status" is telling you that this particular working copy doesn't know about that file. It says nothing about what's in the repository. To actually compare against the repository, you'd use "svn status -u". But if that's your real reason for hating subversion, so be it.
