Ok, so I just announced the my new google code project, and I’m checking in the 0.00000002 alpha version of the code. And this is a media app, so I’ve got some test data, some mp3s. And I didn’t think before I committed, and low and behold subclipse is chugging away in it’s customary slow IDE crappy fashion with 100+MB of mp3s to upload! Oops!
Now, to be honest, I really don’t care about that, it’s just digital detritus after all. But there are really creepy, nasty, vile corporate interests that do care a lot about it. And as much as I think they’re vile, immoral, creepy entities whose members will surely rot in hell, I have to let them, at least momentarily, invade my normally quite pure thoughts… and I gasp in horror at the thought of invertantly violating their corrupt business practices- er I mean copyright laws… and…
Anyway I killed the process midstream.
This is one of those things you don’t think about until something crappy like that happens. Normally a VCS process is simple- commit, comment, done! I really don’t think about it. It’s habit. So what happens when you think you’re committing 100 or so files and maybe that amounts to 1MB and suddenly whoops! And you kill the process?
Well, SVN really has trouble dealing with killed processes, obviously. But thankfully it cleans up after itself really well!
svn cleanup
That’s it. It’s easy. But I didn’t see an svn cleanup option in subclipse, so I did it from the command line.
![[del.icio.us]](http://images.del.icio.us/static/img/delicious.small.gif){kind=small}
One Comment
(project root)->team->cleanup.
The project looks simple, will check it out sometimes
Post a Comment