The best way to learn to make games is to make games. There's no way around it.
Quoth for truth.
ps. what Glaiel said about "teaching game design = stupid," I whole-heartedly agree with. Learn a craft (art or programming) that's vital to completing a game and use it to make games. If you wanted to collab with me and all you wanted to do was design I wouldn't want any part of it.
First of all, Farbs definitely has it. Even in a class, you are going to end up making a game.
Second of all, I thought I would sound like an asshole when I was about to say "heh... game design... heh... don't embarass yourself, learn how to make games, learn programming / art", but I appreciate that others agree.
As I haven't attended a traditional college, I would appreciate it if someone posted some of the game dev. related things they have learned in their CS degrees.
My CS cirriculum wasn't the greatest, because I went to a small private hippie college since I felt like I would just be bitter if I wasn't surrounded by weirdos. Anyways...
The only specifically game-related stuff I learned was OpenGL, which is obviously pretty useful. It was technically an OpenGL class, but the professor (maker of Snood, if you've ever heard of it) had us make a game as a final project. That was probably one of the most useful courses of my whole degree.
The rest of the classes didn't really have anything to do with games, more with web apps, or more often, with theoretical programming topics which only occasionally have applications in the real world, or which someone has already implemented better than you (hashing algorithms, etc.).
Didn't really cover anything else, like I said, the cirriculum was lacking. I think CS is great if you genuinely like programming, but if you are super-super focused on JUST coding games you will probably get bored.