svn command line commit wierdness and Windows XP > Post > Sep 29, 2009 10 p.m.

I thought I was entering into Windows twilight zone, svn wouldn't let me commit on my XP console. Turns out it doesn't like single quotes, so this wouldn't work:

svn ci -m 'This is my message'

I had to do this:

svn ci -m "Windows XP sucks bobo bigtime"

Hope that helps someone keep from pulling their hair out...

Aaron

Delete svn directories > Post > Jan 09, 2009 02 a.m.

Every once in a while we find the need to hack out a bunch of .svn directories, a good example is borrowing a javascript plugin (with 500 nested folders) from a project already committed to a subversion repository. It can be (and really, is) quite painful to go through and remove all those little .svn folders so you can potentially commit the newly-coveted javascript morsel into your new project (if this sounds hackish, it probably is, there must be a better way).

My new favorite hack

rm -rf `find . -type d -name .svn`

Found it here.

Cheers

Global svn ignore > Post > Jan 07, 2009 04 p.m.

I have had the recent annoyance of having svn status reveal every .pyc file in my projects. I usually use eclipse for developing in python/django, but on my old (fluxbox-revived) laptop, eclipse is too much of a hog to run so I settle on gedit (awesome) and the command-line svn, which works just about as great.

The only thing I couldn't figure out is how to get svn to ignore my *.pyc files, and I tried propset and a bunch of other stuff.

Finally

I changed a line in my ~/.subversion/config file, I think it was global-ignore and added *.pyc to the end.

My next svn status? Pretty as can be, and free of pyc files.