For a variety of reasons that will soon become clear over on our Voxeo Developer’s Corner blog, I (Dan York) want to talk a bit about the Git distributed version control system and how it differs from non-distributed version control systems such as CVS and SVN.

Now wait a minute, you say, you aren’t a programmer, so why should you care?

Well, the reality is that I’ve used version control systems for writing books… developing courseware… for web sites… for configuration files… even for home directories of users. Basically, any time I have had a group of files where I want to track revisions to those files – or have wanted to collaborate with someone else and have a solid history of what changes we each have made. Once you start using a version control system, it is simply amazing the number of uses you have for them (only some of which might actually involve programming).

Anyway, “traditional” version control systems (also sometimes called “source code management” (SCM) systems, although there are nuances in the naming) such as the open source Concurrent Versions System (CVS), Subversion (SVN) and the many commercial equivalents all more or less use the model of having a central server from which users “check out” files and then “check in” (or “commit”) any changes they make back to the central server. In more recent years, distributed version control systems (DVCS) have emerged that fundamentally change the paradigm for how a user interacts with their information. Several new open source DVCS’ have emerged, including darcs, mercurial, bazaar and git. For several reasons, I’m currently working with git, but most of what I cover in this and the next episode are similar across the various DVCS systems.

In this first of three episodes I talk about version control systems in general and the different components that make up such a system. I discuss repositories, working copies as well as concepts such as branching and merging – and then wrap up with a few of the issues associated with traditional systems such as CVS and SVN that git sets out to solve.

You can download or play the podcast here:

Or you can watch on YouTube at:

---

If you enjoyed this show, please consider one (or more) of these options:

• subscribing via iTunes
• subscribing to our YouTube account (if you are a YouTube user)
• subscribing to our RSS feed
• following us on Twitter

• following us on FriendFeed

Thank you.

This Voxeo podcast can be found on the web at http://blogs.voxeo.com/ett. If you have comments or feedback about this show, you can either leave comments here on the show blog site or email Dan York.

Technorati Tags: dan york, danyork, emerging communications, emerging tech talk, emerging technology, emergingtechtalk, ett, voxeo, gi, programming, dvcs, development, svn, cvs, version control, scm

Related posts:

1. Emerging Tech Talk #25 – Learning Git, Part 2 – Getting Started with Git
2. Emerging Tech Talk #58 – Book Review: Pragmatic Guide to Git
3. Emerging Tech Talk #26 – Intro to Tropo.com – eComm 209

Tags: DVCS, Git, Programming, SCM, Version Control

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.