This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[wwwdocs] Move some "is a separate page for"-project links into the TOC


In projects/index.html there are now 8 projects for which the TOC entry
only links to a comment about a separate page for that project, e.g.

Projects for the C preprocessor

Links to:
Projects for the C preprocessor
There is a separate project list for the [C preprocessor].

where the [..] is a link to another web page.

This patch simply moves the links to those other pages into the TOC.


After this patch, there are still four projects with full (but short)
descriptions of what the project is about.  I'm not sure what to do
about them.  Ideas?


Index: index.html
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/index.html,v
retrieving revision 1.59
diff -u -3 -p -r1.59 index.html
--- index.html	27 Apr 2005 23:51:41 -0000	1.59
+++ index.html	2 May 2005 23:39:21 -0000
@@ -6,65 +6,36 @@
-<!-- table of contents start -->
-<h1><a name="toc">Table of Contents</a></h1>
+<h1>GCC Projects</h1>
+<p>This is an incomplete list of things you could work on if you want to
+help develop GCC:</p>
-<li><a href="#fix_bugs_in_bts">Fix bugs in our bug tracking system</a></li>
-<li><a href="#beginner_gcc_hackers">Projects for beginner GCC hackers</a></li>
-<li><a href="#gcc_web_pages">Projects for the GCC web pages</a></li>
-<li><a href="#documentation_projects">Projects for improving the GCC documentation</a></li>
-<li><a href="#development_branches">Development Branches</a></li>
-<li><a href="#optimizer_inadequacies">Optimizer inadequacies</a></li>
-<li><a href="#c_preprocessor">Projects for the C preprocessor</a></li>
-<li><a href="#c_front_end">Projects for improving the C front end</a></li>
+<li>If you are new to GCC, start with our list of <a
+    href="beginner.html">projects for beginner GCC hackers.</a></li>
+<li>Investigate bugs and attempt to fix bugs in our <a
+    href="";>bug tracking system</a>,
+    see whether they still are present in current GCC.</li>
+<li><a href="web.html">Projects for the GCC web pages.</a></li>
+<li><a href="documentation.html">Projects for improving the GCC
+    documentation</a>.</li>
+<li>There are several <a href="../cvs.html#devbranches">development
+    branches</a> with projects that you may be able to help out with.</li>
+<li>Investigate and fix some of the known <a href="optimize.html">optimizer
+    inadequacies</a>.</li>
+<li><a href="cpplib.html">Projects for the C preprocessor.</a></li>
+<li><a href="c-frontend.html">Projects for improving the C front end.</a></li>
 <li><a href="#improve_the_installation_procedure">Improve the installation procedure</a></li>
 <li><a href="#simpler_porting">Simpler porting</a></li>
 <li><a href="#other_languages">Other languages</a></li>
 <li><a href="#generalize_the_machine_model">Generalize the machine model</a></li>
 <li><a href="#the_old_problems_file">The old PROBLEMS file</a></li>
-<!-- table of contents end -->
-<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="";>bug
-tracking system</a> and attempt to fix them or see whether they still are
-present in current GCC.</p>
-<h2><a name="beginner_gcc_hackers">Projects for beginner GCC hackers</a></h2>
-<p>If you are new to GCC, start with our <a
-href="beginner.html">projects for beginners</a>.</p>
-<h2><a name="gcc_web_pages">Projects for the GCC web pages</a></h2>
-<p>There is a separate projects list for the <a href="web.html">web
-<h2><a name="documentation_projects">Projects for improving the GCC documentation</a></h2>
-<p>There is a separate projects list for <a
-href="documentation.html">projects for improving the GCC documentation</a>.</p>
-<h2><a name="development_branches">Development Branches</a></h2>
-<p>There are several <a href="../cvs.html#devbranches">development branches</a>
-pursuing various goals.</p>
-<h2><a name="optimizer_inadequacies">Optimizer inadequacies</a></h2>
-<p>We also have a page detailing <a href="optimize.html">optimizer
-inadequacies</a>, if you'd prefer to think about it in terms of problems
-instead of features.</p>
-<h2><a name="c_preprocessor">Projects for the C preprocessor</a></h2>
-<p>There is a separate project list for the <a
-href="cpplib.html">C preprocessor</a>.</p>
-<h2><a name="c_front_end">Projects for the C front end</a></h2>
-<p>There is a separate projects page for the <a
-href="c-frontend.html">C front end</a>.</p>
 <h2><a name="improve_the_installation_procedure">Improve the installation procedure</a></h2>
@@ -98,7 +69,6 @@ href="c-frontend.html">C front end</a>.<
   href="";>PR other/346</a>.</li>
-<hr />
 <h2><a name="simpler_porting">Simpler porting</a></h2>
 <p>Right now, describing the target machine's instructions is done
@@ -143,8 +113,6 @@ now have a way to understand this.</p>
 <p>The scheduler does not do very well on recent RISC machines.  Haifa
 helps but not enough.</p>
-<hr />
 <h2><a name="the_old_problems_file">The old PROBLEMS file</a></h2>
 <p>The following used to be in a file <code>PROBLEMS</code> in the GCC

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]