As an entirely unrelated mention, I’ve put the soerensays2 theme into a Mercurial (Hg) repository, so I can start making some changes to it. I’m just gonna let the log messages so far speak for themselves:

changeset:   4:8d2ac374a722
tag:         tip
user:        Sören Kuklau 
date:        Sat Dec 12 16:50:25 2009 +0100
summary:     pre/code: add Menlo; no need to make it larger any more; no indentation

changeset:   3:dd105c8d8777
tag:         tip
user:        Sören Kuklau 
date:        Sat Dec 12 16:02:48 2009 +0100
summary:     No more columns; 32em instead of 25em; 18px instead of default (e.g. 16px); centered for now

changeset:   2:c1d03afcbb24
user:        Sören Kuklau 
date:        Sat Dec 12 15:43:06 2009 +0100
summary:     Remove the header link for now; was never properly implemented

changeset:   1:741937fb2884
user:        Sören Kuklau 
date:        Sat Dec 12 15:31:50 2009 +0100
summary:     Restore double-em style

changeset:   0:10dd0d874700
user:        Sören Kuklau 
date:        Sat Dec 12 15:28:41 2009 +0100
summary:     Initial

Kudos to Peter Hosey for Lazytwitter-style help with uploading a de-repository’d copy of the WP theme to the Web server via SSH. Looks something like this:

hg archive -t tar -p 'yourtheme' - | ssh example.com 'tar xf - -C ~/path/to/wp-content/themes'

As I’ve noticed with lil’ side projects such as Denis’s all-new Ruby-based CyanChat relay, working with a distributed versioning system feels ridiculously liberating to a developer. I can see what all the fuss is about. I just still question it would work well in all kinds of environments where Subversion does.