Why Git is described as a "content tracking system" -- Part 1

As the next in what might turn into a series on the Git version control system, this post explains what it means to describe Git as a "content tracking" system, a concept that is sometimes a bit difficult for newcomers to wrap their heads around, so let's explain it by way of comparison and a couple trivial Git examples.

How Git keeps track of content history -- a visual approach.

Because the Git version control system takes a rather novel approach to how it stores history, I thought I'd write a very quick-and-dirty explanation of that. Once new users understand how this works, a great deal about Git suddenly becomes a lot clearer. So let's see how well this works out. (I'm still touching up this post, so if you see a typo, leave a comment. Or just leave a comment, anyway. And, yes, I can see Drupal is doing silly things with overly long lines; I'm working on that.)

Working with source RPMs under CentOS.

What's happening here?

Since the online documentation is somewhat hard to come by, this is a short tutorial on how to download and work with source RPM files in CentOS 5.5. And by "work with," I don't necessarily mean compiling and installing; you might simply be interested in examining the source code for one of your CentOS packages, and we'll show you how to do just that.

Installing a package from the Nuxeo Marketplace in 60 seconds.

And what's happening here?

Nuxeo DAM 1.1 in VirtualBox on Ubuntu 10.04, in 60 seconds.

What's this all about?

It's about how to, on your Ubuntu 10.04 system, install VirtualBox, then download and run the spanking new Nuxeo DAM 1.1 digital asset management software in a VirtualBox session. And ... go.

Nuxeo DAM 1.1 on Ubuntu 10.04, in 60 seconds.

So ... you have a Ubuntu 10.04 system, and you want to install the brand new, open source Nuxeo DAM 1.1 Digital Asset Management software in 60 seconds. No problem.

General course discussion mailing list now up.

For the purpose of general discussion about Crash Course's offerings, the delivery model or any other issues related to how Crash Course is writing and publishing online training, I've created the Mailman-based mailing list discuss@lists.crashcourse.ca, which is open to the public and which you can subscribe to by sending a short "subscribe" message to the address discuss-request@lists.crashcourse.ca (as long as I've managed to create and configure that correctly).

Syndicate content