Re:dropbox? (Score 1)

Dropbox + encfs is what I did.

Create an encfs folder within the dropbox folder and everything in it is encrypted locally before going up to the cloud and other machines.

My encfs portion isn't set to maximum security, but by keeping folder/file names encrypted-but-consistent it updates as fast as dropbox always does.
There are resources on the web describing how to set up a repository for minimal dropbox interference.

Data is secure in the "cloud" and secure on your laptop until you mount the drive.
Yes, a stolen laptop could blow away the directory, which may cascade to other machines before you can stop it, but you can "undo" deletions within a limited time-frame.
If you're writing a lot of architecture-specific code, you might want to keep your build trees outside the Dropbox.
2Gb is MORE than enough for day-to-day work that needs to be shared among machines.

For files that are more-or-less read-only (music, etc.) ssh/rsync from the master repository less frequently.