From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] gcc-3.3/criteria.html - simplify
Date: Sun, 02 Sep 2018 21:41:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1809022339280.6216@anthias.pfeifer.com> (raw)
Similar changes as for gcc-3.4/criteria.html, now HTML 5.
Committed.
Gerald
Index: gcc-3.3/criteria.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.3/criteria.html,v
retrieving revision 1.15
diff -u -r1.15 criteria.html
--- gcc-3.3/criteria.html 1 Sep 2018 23:42:03 -0000 1.15
+++ gcc-3.3/criteria.html 2 Sep 2018 21:39:48 -0000
@@ -64,7 +64,7 @@
systems and the most popular microprocessors. Of course, where
possible, the release will support other targets as well.</p>
-<table align="center" border="1">
+<table border="1">
<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 align="center" border="1">
+<table border="1">
<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.3 integration testing.</p>
-<table align="center" border="1">
+<table border="1">
<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 align="center" border="1">
+<table border="1">
<tr><th>Name</th>
<th>Language</th>
<th>Source URL</th>
@@ -356,7 +356,7 @@
<p>In order to measure compile-time performance, we will use the
following unit tests:</p>
-<table align="center" border="1">
+<table border="1">
<tr><th>Name</th>
<th>Language</th>
<th>Source</th>
next reply other threads:[~2018-09-02 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 21:41 Gerald Pfeifer [this message]
2018-09-09 19:36 ` Gerald Pfeifer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.2.21.1809022339280.6216@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).