r771 - webspace/include
DONOTREPLY at icculus.org
DONOTREPLY at icculus.org
Fri May 5 23:01:50 EDT 2006
Author: floam
Date: 2006-05-05 23:01:50 -0400 (Fri, 05 May 2006)
New Revision: 771
Modified:
webspace/include/discuss.php
webspace/include/help.php
webspace/include/status.php
Log:
Monthly floam assault on SVN should be over now.
Modified: webspace/include/discuss.php
===================================================================
--- webspace/include/discuss.php 2006-05-06 02:54:04 UTC (rev 770)
+++ webspace/include/discuss.php 2006-05-06 03:01:50 UTC (rev 771)
@@ -6,33 +6,40 @@
and Bugzilla.</p>
<h2>Mailing Lists</h2>
-<p>There are two mailing lists used by this project. Here's a description and instructions
-for each.
-<h3 class="shell">quake3 at icculus.org</h3>
-<p>There is a general discussion mailing list where you can discuss this project,
-ask for help, announce patches, and anything else that could possibly be talked
-about with the developers and users of icculus.org/quake3.</p>
-<p>To join the list, send a blank e-mail to
-<a href="mailto:quake3-subscribe at icculus.org" class="shell">quake3-subscribe at icculus.org</a>.
-<br />
-To send an e-mail to the list, address it to
-<a href="mailto:quake3 at icculus.org" class="shell">quake3 at icculus.org</a>.
-<br />
-To unsubscribe, send a blank e-mail to
-<a href="mailto:quake3-unsubscribe at icculus.org" class="shell">quake3-unsubscribe at icculus.org</a>.
-<br />
-For more help, send a blank email to
-<a href="mailto:quake3-help at icculus.org" class="shell">quake3-help at icculus.org</a>.
-All of the above information plus more will be sent to you.
+<p>
+ There are two mailing lists used by this project. Here's a description and instructions
+ for each.
+ <div class="indent">
+ <h3 class="shell">quake3 at icculus.org</h3>
+ <p>There is a general discussion mailing list where you can discuss this project,
+ ask for help, announce patches, and anything else that could possibly be talked
+ about with the developers and users of icculus.org/quake3.</p>
+ <p>To join the list, send a blank e-mail to
+ <a href="mailto:quake3-subscribe at icculus.org" class="shell">quake3-subscribe at icculus.org</a>.
+ <br />
+ To send an e-mail to the list, address it to
+ <a href="mailto:quake3 at icculus.org" class="shell">quake3 at icculus.org</a>.
+ <br />
+ To unsubscribe, send a blank e-mail to
+ <a href="mailto:quake3-unsubscribe at icculus.org" class="shell">quake3-unsubscribe at icculus.org</a>.
+ <br />
+ For more help, send a blank email to
+ <a href="mailto:quake3-help at icculus.org" class="shell">quake3-help at icculus.org</a>.
+ All of the above information plus more will be sent to you.
+ </p>
+ </div>
+ <div class="indent">
+ <h3 class="shell">quake3-commits at icculus.org</h3>
+ <p>There is also this read-only mailing list which tracks changes to the
+ <acronym title="Subversion">SVN</acronym> tree. You'll be sent an email each time
+ someone commits a change. This is not normally a high-volume list, but it certainly
+ can be at times. The instructions for this list are identical to the instructions
+ for regular list, just change the <tt>quake3</tt> part of the
+ e-mail addresses to <tt>quake3-commits</tt>.</p>
+ </div>
</p>
-<h3 class="shell">quake3-commits at icculus.org</h3>
-<p>There is also this read-only mailing list which tracks changes to the
-<acronym title="Subversion">SVN</acronym> tree. You'll be sent an email each time
-someone commits a change. This is not normally a high-volume list, but it certainly
-can be at times. The instructions for this list are identical to the instructions
-for regular list, just change the <tt>quake3</tt> part of the
-e-mail addresses to <tt>quake3-commits</tt>.</p></p>
+
<h2 title="Internet Relay Chat">IRC</h2>
<p>To join the <acronym title="Internet Relay Chat">IRC</acronym> channel, aim
your client at <a href="irc://irc.freenode.net/icculus.org/quake3">
Modified: webspace/include/help.php
===================================================================
--- webspace/include/help.php 2006-05-06 02:54:04 UTC (rev 770)
+++ webspace/include/help.php 2006-05-06 03:01:50 UTC (rev 771)
@@ -203,37 +203,37 @@
<del>blame</del> credit to.</p>
<h2>Generating Patches</h2>
-<p>If you know how to code, but never made a patch before, that's okay. Here's the 10¢
-survival guide to generating patches.</p>
-<ul>
- <li>
- <h3>From <acronym title="Subversion">SVN</acronym></h3>
- <p>If you checked the source code out with <acronym title="Subversion">SVN</acronym>,
- 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:</p>
- <ul>
- <li>Create a patch named <em class="shell">amazing_new_feature.patch</em>:<br />
- <tt>svn diff > <em>amazing_new_feature.patch</em></tt></li>
- <li id="patch">Apply a patch <em class="shell">amazing_new_feature.patch</em>:<br />
- <tt>patch -p0 -i <em>amazing_new_feature.patch</em></tt></li>
- </ul>
- </li>
- <li>
- <h3>From a tarball or other release</h3>
- <p>If you didn't get the source code via <acronym title="Subversion">SVN</acronym>,
- or for some reason that doesn't work for your situations, here's how to generate
- them using the tried-and-trusted <tt>diff</tt> tool between
- two files:</p>
- <ul>
- <li>Create a patch named <em class="shell">amazing_new_feature.patch</em> between <em class="shell">oldfile</em> and <em class="shell">newfile</em>:<br />
- <tt>diff -u <em>oldfile</em> <em>newfile</em> > <em>amazing_new_feature.patch</em></tt></li>
- <li>Create a patch named <em class="shell">amazing_new_features.patch</em> between directory <em class="shell">olddir</em> and <em class="shell">newdir</em>:<br />
- <tt>diff -Naur <em>olddir</em> <em>newdir</em> > <em>amazing_new_features.patch</em></tt></li>
- <li>Applying a patch is the same as with SVN, see <a href="#patch">above</a>.</li>
- </ul>
- </li>
-</ul>
+<p>
+ If you know how to code, but never made a patch before, that's okay. Here's the 10¢
+ survival guide to generating patches.
+ <div class="indent">
+ <h3>From <acronym title="Subversion">SVN</acronym></h3>
+ <p>If you checked the source code out with <acronym title="Subversion">SVN</acronym>,
+ 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:</p>
+ <ul>
+ <li>Create a patch named <em class="shell">amazing_new_feature.patch</em>:<br />
+ <tt>svn diff > <em>amazing_new_feature.patch</em></tt></li>
+ <li id="patch">Apply a patch <em class="shell">amazing_new_feature.patch</em>:<br />
+ <tt>patch -p0 -i <em>amazing_new_feature.patch</em></tt></li>
+ </ul>
+ </div>
+ <div class="indent">
+ <h3>From a tarball or other release</h3>
+ <p>If you didn't get the source code via <acronym title="Subversion">SVN</acronym>,
+ or for some reason that doesn't work for your situations, here's how to generate
+ them using the tried-and-trusted <tt>diff</tt> tool between
+ two files:</p>
+ <ul>
+ <li>Create a patch named <em class="shell">amazing_new_feature.patch</em> between <em class="shell">oldfile</em> and <em class="shell">newfile</em>:<br />
+ <tt>diff -u <em>oldfile</em> <em>newfile</em> > <em>amazing_new_feature.patch</em></tt></li>
+ <li>Create a patch named <em class="shell">amazing_new_features.patch</em> between directory <em class="shell">olddir</em> and <em class="shell">newdir</em>:<br />
+ <tt>diff -Naur <em>olddir</em> <em>newdir</em> > <em>amazing_new_features.patch</em></tt></li>
+ <li>Applying a patch is the same as with SVN, see <a href="#patch">above</a>.</li>
+ </ul>
+ </div>
+</p>
<p>For more information on <tt>diff</tt>, <tt>patch</tt>,
and <tt>svn</tt>, read their respective <tt>man</tt>
and <tt>info</tt> pages. For a more in-depth guide on Subversion take
Modified: webspace/include/status.php
===================================================================
--- webspace/include/status.php 2006-05-06 02:54:04 UTC (rev 770)
+++ webspace/include/status.php 2006-05-06 03:01:50 UTC (rev 771)
@@ -132,20 +132,22 @@
on new cvars and commands introduced in this project.</p>
<h2>The Future</h2>
-<h3>Release Criteria</h3>
-<p>Before a release can occur, the following must occur for each platform:</p>
-<ol class="indent">
- <li>Testing of <em>Quake III: Arena</em> single- and multi-player.</li>
- <li>Testing of <em>Quake III: Team Arena</em> single- and multi-player.</li>
- <li>Testing of at least one other Quake 3 modification. Possibly
- <a href="http://www.urbanterror.net/">Urban Terror</a>,
- <a href="http://www.rq3.com/">Reaction Quake3</a>, or any other popular
- modification that puts the engine through its paces.</li>
- <li>An installer which includes all <a href="?page=getdata">up-to-date id <tt>pk3</tt>
- files</a>, requires original CD-ROM. Users might need to copy the
- <tt>pak0.pk3</tt> file themselves.</li>
-</ol>
-
+<div class="indent">
+ <h3>Release Criteria</h3>
+ <p>Before a release can occur, the following must occur for each platform:</p>
+ <ol class="indent">
+ <li>Testing of <em>Quake III: Arena</em> single- and multi-player.</li>
+ <li>Testing of <em>Quake III: Team Arena</em> single- and multi-player.</li>
+ <li>Testing of at least one other Quake 3 modification. Possibly
+ <a href="http://www.urbanterror.net/">Urban Terror</a>,
+ <a href="http://www.rq3.com/">Reaction Quake3</a>, or any other popular
+ modification that puts the engine through its paces.</li>
+ <li>An installer which includes all <a href="?page=getdata">up-to-date id <tt>pk3</tt>
+ files</a>, requires original CD-ROM. Users might need to copy the
+ <tt>pak0.pk3</tt> file themselves.</li>
+ </ol>
+</div>
+<div class="indent">
<h3>Roadmap</h3>
<ul>
<li>
@@ -178,7 +180,7 @@
<p><em>Note: The above is a list of steps that <strong>remain to be completed</strong>,
so the lists will get shorter as release approaches. Items already completed are
not on the roadmap.</em></p>
-
+</div>
<h2>PunkBuster Support</h2>
<p><a href="http://www.evenbalance.com/">Even Balance</a>'s Punkbuster support can never
be included with any open-source version of Quake 3 due to it being removed from the
More information about the quake3-commits
mailing list