PATCH for Re: Patch to move warning for X<=Y<=Z from -W to -Wparentheses

[Gerald Pfeifer <gerald at pfeifer dot com>]

On Sat, 7 Aug 2004, Joseph S. Myers wrote:
> These look like reasonable descriptions to go somewhere on the web pages
> (contribute.html?).

Agreed.  Done thusly.

As a general note, I'll be gone for three weeks, and appreciate if
some others will help out with reviewing/making web page changes
during that period.

Gerald

Index: contribute.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v
retrieving revision 1.58
diff -u -3 -p -r1.58 contribute.html
--- contribute.html	4 Sep 2004 12:53:18 -0000	1.58
+++ contribute.html	19 Sep 2004 18:52:56 -0000
@@ -24,6 +24,7 @@ contributions must meet:</p>
 <li><a href="#docchanges">Documentation Changes</a></li>
 <li><a href="#webchanges">Web Site Changes</a></li>
 <li><a href="#patches">Submitting Patches</a></li>
+<li><a href="#announce">Announcing Changes (to our Users)</a></li>
 </ul>

 <hr />
@@ -278,5 +279,19 @@ no-one else will need to apply it to the
 totally new files may be omitted (especially if large) since they can be
 accessed directly from the repository.</p>

+
+<h2><a name="announce">Announcing Changes (to our Users)</a></h2>
+
+<p>Everything that requires a user to edit his Makefiles or his source code
+is a good candidate for being mentioned in the release notes.</p>
+
+<p>Larger accomplishments, either as part of a specific project, or long
+term committment, merit mention on the front page.  Examples include projects
+like tree-ssa, new backends, major advances in optimization or standards
+compliance.</p>
+
+<p>The gcc-announce mailing list serves to announce new releases and changes
+like frontends or backends being dropped.</p>
+
 </body>
 </html>