So, you have your old Subversion repo, and you want to move to Mercurial. Sure, you could check in an export of the SVN repo's HEAD, but then you've lost all the history of that repository. Thankfully, the folks that cooked up Mercurial made a conversion extension just for this task.

So my brain has been tainted by that which is the fundamentals of DVCSes. I tried taking a look at git first, and I saw what I would call "bugs" championed as features of immense flexibility. I couldn't get on board.

Mercurial, however, seems to have a much more sane structure to it. Setting up a publishing repo (a replacement for a centralized repository) also seems to be a lot simpler. Making your branches accessible to others is as simple as hg serve -d, although that doesn't leave much way in the room of user management.

I wanted a locked down repository, and an administration frontend would be a plus. A friend introduced me to RhodeCode as a possible option. I have found it to be simple, intuitive, sturdy, and fast thus far. Installation is simple too.

Telnet, FTP, and SVN all have one thing in common. They'll transmit passwords over plain-text. Lovely. Unfortunately, this doesn't bode well for the security freak that exists in all of us in various sizes.

The svnserve daemon can only handle one protocol, the SVN protocol, denoted by the svn:// URI. However, DAV modules for SVN exist that plug into Apache, which allows Apache to mingle about with the DB files that Apache stores on disk. These files represent the repository and its state over time, and Apache can manage them instead of svnserve, allowing you to add all sorts of nice Apache features to your SVN repository. Like SSL encryption.

Cyanogen 7 for the Nook Color has a bit of a problem. The included Gallery application, when you crop an image to use as a wallpaper in any launcher, crops the image down to a size suitable for a smartphone. However, we're dealing with a 1024x600 resolution screen. The end result is a blurry and unsatisfying desktop on your Nook Color.

There's a way around this, but this problem has been present since late 2010, as evident in the XDA-Developers forum.

The solution is straight-forward: There are many apps out there that are capable of setting the desktop wallpaper on Android. There is a plethora of apps out there that solve this problem. One in particular is the simple "Crop Wallpaper" [Market Link].

Install Crop Wallpaper, and then run it. The menus are a bit bare for folder exploration, but it works. Then, just select an image, crop it as you see fit, and set it. Back out to your home screen, and bam, you've got a native resolution desktop that no longer irks your OCD.

So, you bought a new Nook Color. Oddly, you notice that the menus only report "1GB" of sideload storage, and your flashes of Cyanogen's nightly won't get past the spinny-loady screen. Then you find out that Barnes & Noble has decided to sacrifice the size of the sideload (/media) partition in favor giving space for the user data (/data). And in doing so, they broke half of the wonderful things you tend to do with a rooted Android device.

So now you want to undo it. It's only a matter of repartitioning a disk, right?