"I have recently learned git for version control, having used Subversion for four years and CVS for four years prior to that. It has a lot of nice features and I thought of a good application: restoration of lost history on a Subversion repository..." --
* To understand git read this completely => http://www.newartisans.com/blog_assets/git.from.bottom.up.pdf

"The topic of switching from CVS to something else regularly came forward but nobody did anything. The net result is that several documentation are now maintained outside of the debian-doc repository because their respective maintainers didn’t want to stay with CVS. After noticing that the developers-reference also switched to SVN, I decided to convert the whole debian-doc CVS repository and import it in the new “ddp” SVN repository on Alioth. This is now done..."

"Every clone of a Mercurial repository can act as a consistent, fully functional repository itself.This is a very useful property of a DVCS; one that you can take advantage of to make development a lot easier, especially for teams that are dispersed in multiple places of the globe..." — Mercu

"Mercurial [Hg for short] is a Distributed Version Control System. Instead of using a single repository per project, each developer can have their own repository." -- via http://understandinglimited.com/2008/08/07/ff-h/

etckeeper is a collection of tools to let /etc be stored in a git, mercurial, darcs, or bzr repository. It hooks into apt (and other package managers including yum and pacman-g2) to automatically commit changes made to /etc during package upgrades.

If you want to convert audio files on Linux, Audio-convert-mod is worth a try. Audio-convert-mod is a simple and easy-to-use audio file converter. It supports many formats, includes: MP3, OGG, FLAC, WAV, AAC/MP4/M4A, MAC/Monkey’s Audio/APE, MPC (Musepack), WV (wavpack) etc. In addition, with Audio-convert-mod, you can also batch convert audio files.

There are a number of version control systems available. Originally there was RCS, which was suitable for individuals, but not really suitable for groups of people. It evolved into CVS, which worked pretty well for years, and then Subversion came along, making a better CVS than CVS itself.

Folks using RubyForge have been requesting alternatives to CVS and Subversion for a while - there are feature requests in for Mercurial, Monotone, Darcs, and Git. Of those, Git seems to be the most popular at the moment, so thanks to Garry Dolley's excellent tutorial on Gitosis, RubyForge now supports Git as one of the SCM choices. Huzzah! ..."

Sharing code between projects is still not a trivial matter with subversion. Especially if you are familiar with SourceSafe, you will find that subversion makes it hard to share code. Subversion seems to be really great in creating a version mess and good in solving one, but the reason I need source code control is to prevent such a mess.