From 319c0c8f120c5ad429010d65666a58fec7f0615a Mon Sep 17 00:00:00 2001
From: floam Quake 3 source code was released on August 20th by the fine folks at id Software. We thank them for that, and are continuing the mission of producing a Quake 3 that is without fault. Quake 3 source code was released on August 20th by the fine folks at id Software.
+We thank them for that, and are continuing the mission of producing a Quake 3 that is
+without fault. This project aims to build upon id Software's Quake 3 source code release.
-The source was released on August 20, 2005 under the GPL license. Since then, we have
-been feverishly cleaning up, fixing bugs, and adding features. Our eventual
-goal is to have created the Quake 3 source code distribution upon which people
-base their games and mods. Our focus is initially
-to get the game working with our updates on Mac OS X, Windows, and Linux. Sane new features are also welcome. Modern graphical upgrades (bloom lighting, etc) would have to be disabled by default.
+ This project aims to build upon id Software's Quake 3 source code release. The source
+code was released on August 20, 2005 under the
+GPL.
+Since then, we have been feverishly cleaning up, fixing bugs, and adding features. Our
+eventual goal is to have created the Quake 3 source code distribution upon which
+people base their games, ports, and mods. Our focus initially is to get the game working
+with our updates on Mac OS X, Windows, and Linux. Sane new features are also welcome.
+Modern graphical upgrades (ie. bloom lighting) would have to be disabled by default.
While a lot is left to be done, quite a few goals have been met already. Quake 3
-now works natively on x86_64 and PowerPC architectures, plus the game builds and runs
-on FreeBSD. SDL is now used for input, OpenGL context management and sound, making the game a lot easier
-to port to new platforms and architectures than it was before. Security holes and other
-problems have been repaired. A more in-depth database of new features and working status
-on different platforms is in the Status section.What's the point?
-Progress
Current goals for 1.34 (SVN is 1.33, last id build was 1.32) include:
+Current goals for 1.34 (SVN is 1.33, last id +build was 1.32) include:
(This part assumes Windows users are using Cygwin. If you aren't, -TortoiseSVN is a good client.)
+( This part assumes Windows users are using Cygwin. If you aren't, +TortoiseSVN is a good client. )
Not everyone who knows C knows how to use diff (the tool -you need to create patches with), and not everyone is making patches against the C code. -That's okay, here's the 10¢ survival guide to making patches:
+ +The preferred way to get the ball rolling on a patch is to file a +Bugzilla bug for your request with the patch attached +to it and then send a notice to the mailing list about it. If you're really so lazy that +you can't do this, we would prefer you at least mail +it to zakk@icculus.org rather than not do anything at all.
+ +Please don't send in patches that you didn't create. You can feel free to alert people +and discuss anything on the mailing list, but please only submit patches for +inclusion if you are the original creator!
+ +If you know how to code, but never made a patch before, that's okay. Here's the 10¢ +survival guide to generating patches.
If you checked the source code out with SVN, + the client makes it rather easy to generate patches. In fact it's a function + of the client itself. Once you've made a change in your checkout that is + not upstream, here is how you use it:
+For more information on SVN take a look at the + SVN book and the info pages for + svn.
+If you didn't get the source code via SVN, + or for some reason that doesn't work for your situations, here's how to generate + them using the tried-and-trusted diff tool between + two files:
+For more information on diff and patch, + read their man-pages.
+For more information on diff and patch, -read their man-pages.
-The prefered way to get the ball rolling on a patch is to file a bug -for your request with the patch attached to it and then send a notice to the mailing list -about it. If you're really so lazy that you can't do this, we would prefer you at least -mail it to zakk@icculus.org rather than not do -anything.
diff --git a/web/include/status.php b/web/include/status.php index 2f42343..07971ba 100644 --- a/web/include/status.php +++ b/web/include/status.php @@ -48,7 +48,7 @@