Tuesday the 24th is Fat Tuesday

We're eating pancakes at my church from 5-7PM

All you can eat pancakes $4 for adults. Student discount available.

Church is Saint Stephen's on the corner of Woodruff & High.

Last night, I worked a bit on the Debian package for darcs. darcs is an advanced revision control system, "two senses in which it is supposed to be advanced: 1) each copy of the source is a fully functional branch, and 2) underlying darcs is a consistent and powerful theory of patches.". Darcs is also written in Haskell, which makes it even more cool.

When I did my first big group project in college, I started using CVS and completely loved it. I tried subversion for a while last year, and at home and work I'm currently using arch / tla. I'm excited about these two distributed revision control systems, tla and darcs.

Keeping packages in VC: Since the author of darcs, David Roundy, is apparently a Debian user (and a skillful one at that), I expect this package to be a joy to take care of. At his suggestion, I'm going to keep my changes in darcs itself, and I figure that while I'm at it, I'll keep all my packages in darcs.

I'm debating a bit about how to go about this, though. I could keep just the "debian" directory in version control, but then if I have to change the upstream sources (like the Makefile), then I couldn't track that. On the other hand, if I keep all the upstream sources in VC, then I'd have to sorta pound on the repository whenever there's a new release, with a bunch of big changes. Not too bad, I guess. What do those of you who keep packages in version control do?

I was very pleased to see Colin's blog entry yesterday about Intel support of its Centrino chipset for Linux. I've been sending mail to them every couple of weeks for the last 8 months or so.