[wwwdocs] Move gcc-3.4/criteria.html to HTML 5

Message ID alpine.LSU.2.21.1809102100540.6216@anthias.pfeifer.com
State New
Headers show
Series
  • [wwwdocs] Move gcc-3.4/criteria.html to HTML 5
Related show

Commit Message

Gerald Pfeifer Sept. 10, 2018, 7:03 p.m.
...and remove "DRAFT" from its title on the way, ahem.

Applied.

Gerald

Patch

Index: gcc-3.4/criteria.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.4/criteria.html,v
retrieving revision 1.9
diff -u -r1.9 criteria.html
--- gcc-3.4/criteria.html	2 Sep 2018 21:30:48 -0000	1.9
+++ gcc-3.4/criteria.html	10 Sep 2018 19:01:00 -0000
@@ -2,13 +2,13 @@ 
 <html>
 
 <head>
-<title>DRAFT: GCC 3.4 Release Criteria</title>
+<title>GCC 3.4 Release Criteria</title>
 <link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css" />
 </head>
 
 <body>
 
-<h1>DRAFT: GCC 3.4 Release Criteria</h1>
+<h1>GCC 3.4 Release Criteria</h1>
 
 <p>This page provides the release criteria for GCC 3.4.  GCC 3.4 will
 not be released until these criteria have been met.  This page
@@ -64,7 +64,7 @@ 
 systems and the most popular microprocessors.  Of course, where
 possible, the release will support other targets as well.</p>
 
-<table border="1">
+<table class="center">
 <caption>Primary Evaluation Platforms</caption>
 <tr><th>Chip</th>     <th>OS</th>                  
                       <th>Triplet</th>
@@ -123,7 +123,7 @@ 
 team, will make reasonable efforts to assist these volunteers by
 answering questions and reviewing patches as time permits.</p>
 
-<table border="1">
+<table class="center">
 <caption>Secondary Evaluation Platforms</caption>
 <tr><th>Chip</th>     <th>OS</th>
                       <th>Triplet</th>
@@ -200,7 +200,7 @@ 
 to general information about a package and a source URL.  Versions
 shown here are used for GCC 3.4 integration testing.</p>
 
-<table border="1">
+<table class="center">
 <caption>Integration Tests</caption>
 <tr><th>Name</th>
     <th>Language</th>
@@ -313,7 +313,7 @@ 
 Therefore, we will use the following benchmarks for measuring code
 quality:</p>
 
-<table border="1">
+<table class="center">
 <tr><th>Name</th>
     <th>Language</th>
     <th>Source URL</th>
@@ -357,7 +357,7 @@ 
 <p>In order to measure compile-time performance, we will use the
 following unit tests:</p>
 
-<table border="1">
+<table class="center">
 <tr><th>Name</th>
     <th>Language</th>
     <th>Source</th>