Linus Torvalds visits Google to share his thoughts on git, the source control management system he created two years ago.

He slams CVS and Subversion really badly -- maybe a little too badly?

Learn basic Git concepts and compare Git with Subversion. Distributed version control systems (DVCSs) offer a number of advantages over centralized VCSs, and for Subversion users looking to explore this model, Git is a great place to start. Using Subversion as a baseline, this first of two articles shows how to install Git, set up a remote repository, and begin using basic Git commands.

Subversion is a free/open-source version control system. That is, Subversion manages files and directories, and the changes made to them, over time. This allows you to recover older versions of your data, or examine the history of how your data changed. In this regard, many people think of a version control system as a sort of "time machine".

Subversion is a version control system: It keeps a record of changes over the lifetime of a file, allowing you to revert to an earlier version at will. It's particularly useful for code projects, but it can handle, and be useful for, pretty much any type of file (e.g., for tutorials!). It's available as a package for most Linux distros, or as source from the web site.

"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

If you’re a Linux user, you’ve likely come across Git at some point, perhaps while trying to download a new program or looking into version control systems like CVS or Subversion. Git is the revision control system created by the Linux kernel’s famous Linus Torvalds due to a lack of satisfaction with existing solutions.

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.

KDE announced today that the one millionth commit has been made to its Subversion-based revision control system. Schumacher attributes this growth to the strength of both KDE's products and vision.

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.