If you learned git, you may be tempted that all version control systems are complex beasts with bizarre, inscrutable commands. This ain't so. Mercurial and Bazaar have commands that are obvious to english speakers.
$ bzr help Bazaar 2.5.0 -- a free distributed version-control tool http://bazaar.canonical.com/
Basic commands: bzr init makes this directory a versioned branch bzr branch make a copy of another branch
bzr add make files or directories versioned bzr ignore ignore a file or pattern bzr mv move or rename a versioned file
bzr status summarize changes in working copy bzr diff show detailed diffs
bzr merge pull in changes from another branch bzr commit save some or all changes bzr send send changes via email
bzr log show history of changes bzr check validate storage
bzr help init more help on e.g. init command bzr help commands list all commands bzr help topics list all help topics
If GIT isn't your thing then I suggest checking out Bazaar it is better then SVN but you can still keep your SVN style workflow of committing to a central location.
I've found it quite useful in our office. It makes it easy to make sure everyone is working on the same codebase while also giving you the option of taking the latest version and going off by yourself then later merging it all back in without problems.
I know bazaar isn't an "in" thing which is extremely popular but it's been a really useful tool and suggest you take a look if you're not so busy.
/sales pitch
I agree with many of the author's points. I tend to stay with mainstream git and get along fine. I used to use Canonical's bzr as my first DVCS and thought it was both easy and reliable. With everyone switching to git several years ago though I really didn't have much choice but to switch. I'd recommend the whole world switch to bzr as it looks like it is even more mature now than Fossil. That won't happen though so I'll be staying with git.
There's also Bazaar (bzr). It's a distributed VCS and is opensource. It was created by Canonical for Ubuntu. Hosting on http://www.launchpad.net is free.
I have no idea what VCS is best. I just thought I'd bring up another option.
I guess it's difficult to have serial revision numbers in git because it's a distributed VCS. Since there isn't a central repository to hand out authoritative auto-incrementing integers, any numbering scheme you come up with can potentially conflict with another repository's revision numbers.
In bzr, for example, revision numbers are auto-incrementing integers, but they're virtually meaningless unless you know whose repository you're talking about. When you merge, you end up with revision numbers like 123.4.56 which is not much better than a random hash.