One of the downsides of svn vs git (perhaps central vs distributed versioning itself??) is that when you delete a file from a local copy1 of a repo. and then update the local copy2 it doesn’t delete the file. Even if the file hasn’t changed. I can understand if the local copy2 has changed the file but, even if it hasn’t changed??? Come on…. that’s a bad design… Maybe because it’s a centralized repository?? On second thoughts, no even that doesn’t make sense. Even if it’s a centralized repo you do have a backup of the file in a previous revision right?? So what’s the point of not deleting it in the local copy… it just creates extra work for the developer really…
And really ..WTF is this error message…??
svn: warning: Tree conflicts can only be resolved to ‘working’ state; ‘misc/ssh3.py’ not resolved
Please.. this is enforcing policy not providing mechanism.
And wtf is with svn: Commit failed (details follow):
svn: ‘/home/XXxXXXX/workspace/DemandMedia/css/trunk/pyne2/misc/ssh3.py’ is scheduled for addition, but is missing
….Really??? why do you care. it’s anyways supposed to be deleted.. and you are expected to have a copy.anyway it’s not the same as if you delete you can’t get it back………