What happens when nobody will take responsibility for a standard that the web relies on?
Following user requests, I’ve uploaded a new version of rmrip which takes a command-line argument specifying your configuration file:
./rmrip.py foo.conf
As the user himself implied, this has the added bonus of making it more crontab-friendly e.g. you can have a crontab entry saying:
Say you want to see both the log and diff of a given svn version, just the differences between it and the previous version, plus log message (i.e. what was committed, and why, for version NUM) The following will work at a bash command prompt:
$ r=NUM; rr=-r`expr $r - 1`:$r; svn log -r$r; svn diff $rr
It looks a bit unwieldy, but you can keep pressing the up arrow and home key, and re-editing NUM, multiple times to look at multiple changes:
Simon Willison mentioned a while back a link to help on how to undo a svn commit in subversion (more a kind of internal branching than an actual undo, of course: but that’s subversion). That’s all very well, but how about undoing the log message for a particular commit?
After having been stuck on version 2.0.1 for over two years, I’ve just upgraded to the most recent version, 2.5.1. The only hiccup was needing to ask my web provider to give me a new MySQL database: since 2.5, Wordpress has required MySQL 4.0 or newer.
Otherwise, it all seems to be running very smoothly. Do let me know if you see anything crazy. I hope to upgrade more frequently in future, as it was a far better experience than I’d expected.