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.
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.)
As of yesterday, there's a new snapshot of Nuxeo DAM (Digital Asset Management) for Ubuntu --
nuxeo-dam-jboss_1.1-SNAPSHOT-20100702_all.deb -- and a lot of outstanding issues from the previous snapshot have been cleaned up. Among other things, "nuxeodam" user and group accounts have been created to act as owners of the running process, and lots of other little improvements. All in all, very nice so, at this point, I'm reduced to nitpicking:
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
email@example.com, which is open to the public and which you can subscribe to by sending a short "subscribe" message to the address
firstname.lastname@example.org (as long as I've managed to create and configure that correctly).