Patch to projects lists

["Joseph S. Myers" <jsm at polyomino dot org dot uk>]

The projects lists have various statements of the form "contact X before
working on Y".  While it's likely that at one point X was working on Y or
had ideas about how to do Y, these statements are pretty old so X is
unlikely currently to be doing anything related to what they once were
doing on Y.  In any case, good practice is for people to send such queries
to the public lists rather than individuals.  Accordingly this patch
removes such statements from the main two projects lists
(projects/index.html and projects/beginner.html).  OK to commit?

(If you think one of the items I'm removing these comments from is
obsolete in its entirety, or otherwise needs updating, please submit a
followup patch to update or remove it as necessary.)

-- 
Joseph S. Myers               http://www.srcf.ucam.org/~jsm28/gcc/
    jsm@polyomino.org.uk (personal mail)
    jsm28@gcc.gnu.org (Bugzilla assignments and CCs)

Index: beginner.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/beginner.html,v
retrieving revision 1.47
diff -u -r1.47 beginner.html
--- beginner.html	10 Jun 2004 21:38:32 -0000	1.47
+++ beginner.html	29 Jun 2004 20:05:51 -0000
@@ -33,6 +33,9 @@
 well.  Unfortunately, for this we only have an <a
 href="http://gcc.gnu.org/onlinedocs/gccint/Trees.html";>incomplete, C/C++ specific manual</a>.</p>
 
+<p>Remember to <a href="../contributewhy.html">keep other developers
+informed</a> of any substantial projects you intend to work on.</p>
+
 <h2>Bug patrol</h2>
 
 <p>These projects all have to do with bugs in the compiler, and our
@@ -683,10 +686,7 @@
 </pre>
 
 <p>Unfortunately, the technique is very poorly documented and may need
-extending to other conditional operations (setcc, movcc) as well.
-Contact Bernd
-Schmidt &lt;<a href="mailto:bernds@redhat.com";>bernds@redhat.com</a>&gt;
-before beginning any work on this.</p>
+extending to other conditional operations (setcc, movcc) as well.</p>
 </li>
 
 <li>Find hooks in the machine-independent code which aren't used by
@@ -902,11 +902,7 @@
 <a href="http://www.ncsa.uiuc.edu/~wendling/tree.html";>third party,
 general manual</a>.  Both of them are incomplete.  Several people have
 written partial manuals on implementing new front ends: look at our
-<a href="../readings.html">readings list</a>.</p>
-
-<p>Michael Dupont &lt;<a
-href="mailto:mdupont777@yahoo.com";>mdupont777@yahoo.com</a>&gt;
-is working on this, so contact him first.</p></li>
+<a href="../readings.html">readings list</a>.</p></li>
 
 <li>Roll information in external documents into the official manual.
 
Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/index.html,v
retrieving revision 1.42
diff -u -r1.42 index.html
--- index.html	1 Feb 2004 20:09:21 -0000	1.42
+++ index.html	29 Jun 2004 20:05:51 -0000
@@ -78,6 +78,9 @@
 
 <h1>GCC Projects</h1>
 
+<p>Remember to <a href="../contributewhy.html">keep other developers
+informed</a> of any substantial projects you intend to work on.</p>
+
 <h2><a name="fix_bugs_in_bts">Fix bugs in our bug tracking system</a></h2>
 <p>You can investigate bugs in our <a href="http://gcc.gnu.org/bugzilla/";>bug
 tracking system</a> and attempt to fix them or see whether they still are
@@ -142,9 +145,7 @@
 implementation status is available.</p>
 
 <h2><a name="improve_the_haifa_scheduler">Improve the Haifa scheduler</a></h2> (haifa-sched.c, loop.[ch],
-unroll.c, genattrtab.c): (contact <a
-href="mailto:law@redhat.com";>law@redhat.com</a> before starting any
-serious haifa work)
+unroll.c, genattrtab.c):
 
 <ul>
   <li>Fix/add comments throughout the code.  Many of the comments are
@@ -188,9 +189,6 @@
 <p>It can probably also be used to improve the reg-stack pass of the
 compiler.</p>
 
-<p>Contact <a href="mailto:law@redhat.com";>law@redhat.com</a> if
-you're interested in working on lazy code motion.</p>
-
 <h2><a name="miscellaneous_ideas">Miscellaneous ideas:</a></h2>
 
 <p>The following are some miscellaneous ideas for GCC projects to work
@@ -303,9 +301,6 @@
 <h2><a name="format_checking">Format (<code>printf</code>, <code>scanf</code> and
 <code>strftime</code>) checking:</a></h2>
 
-<p>Contact <a href="mailto:jsm28@cam.ac.uk";>jsm28@cam.ac.uk</a> before
-doing any substantial format checking work.</p>
-
 <ul>
 
 <li>Make re-entrant: eliminate global state used for <code>$</code>
@@ -410,9 +405,6 @@
 
 <h2><a name="improve_the_installation_procedure">Improve the installation procedure</a></h2>
 
-<p>Contact <a href="mailto:zackw@stanford.edu";>zackw@stanford.edu</a>
-before working on improvements to installation.</p>
-
 <ul>
 
 <li>See <a href="http://gcc.gnu.org/ml/gcc/2000-11/msg00556.html";>a
@@ -620,10 +612,7 @@
 example, through a particular loop where the variable is mostly used,
 or outside of a particular loop where the variable is not used.  (The
 latter is nice because it might let the variable be in a register most
-of the time even though the loop needs all the registers.)
-
-Contact <a href="mailto:meissner@redhat.com";>meissner@redhat.com</a>
-before starting any work on live range splitting.</p>
+of the time even though the loop needs all the registers.)</p>
 
 <h3><a name="detect_dead_stores_into_memory">Detect dead stores into memory?</a></h3>
 
@@ -633,9 +622,7 @@
 address).</p>
 
 <p>This can be modeled as a partial redundancy elimination/lazy code
-motion problem.  Contact <a
-href="mailto:law@redhat.com";>law@redhat.com</a> before working on dead
-store elimination optimizations.</p>
+motion problem.</p>
 
 <h3><a name="loop_optimization">Loop optimization</a></h3>
 
@@ -699,9 +686,6 @@
 
 <p>Consider hoisting common code up past conditional branches or tablejumps.</p>
 
-<p>Contact <a href="mailto:law@redhat.com";>law@redhat.com</a> before
-working on code hoisting.</p>
-
 <h3><a name="trace_scheduling">Trace scheduling</a></h3>
 
 <p>This technique is said to be able to figure out which way a jump