public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <burnus@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 0e6e94f4bc1743b99c642920ed2af0e11beb1dd2
Date: Tue, 17 May 2022 09:48:03 +0000 (GMT)	[thread overview]
Message-ID: <20220517094803.68BDE3858D3C@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  0e6e94f4bc1743b99c642920ed2af0e11beb1dd2 (commit)
      from  f7651427bfa17d0a460dd63285d4da9130d21f33 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 0e6e94f4bc1743b99c642920ed2af0e11beb1dd2
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Tue May 17 11:44:32 2022 +0200

    Fix gcc.css for omptable
    
    * htdocs/gcc.css: Add thead/tbody between table.omptable and td/td;
      change 'tr.separator' to 'tr' as 'thead tr' captures this.
    * htdocs/projects/gomp/index.html: Remove 'class=separator' on <tr>.

diff --git a/htdocs/gcc.css b/htdocs/gcc.css
index 29807a24..77d01ee0 100644
--- a/htdocs/gcc.css
+++ b/htdocs/gcc.css
@@ -116,9 +116,9 @@ table.cxxdrstatus tr.separator { background: #f2f2f9; }
 table.cxxdrstatus { width: 65%; }
 
 /* OpenMP status tables. */
-table.ompstatus th, table.cxxstatus td { border: 1px solid gray; }
-table.ompstatus td:nth-child(2) { text-align:center; }
-table.ompstatus tr.separator { background: #f2f2f9; }
+table.ompstatus thead th, table.cxxstatus thead td { border: 1px solid gray; }
+table.ompstatus tbody td:nth-child(2) { text-align:center; }
+table.ompstatus thead tr { background: #f2f2f9; }
 
 /* Padded tables. */
 table.padding5 th, td { border: 1px solid gray; padding:5px; }
diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html
index 42932c77..52991c02 100644
--- a/htdocs/projects/gomp/index.html
+++ b/htdocs/projects/gomp/index.html
@@ -182,7 +182,7 @@ than listed, depending on resolved corner cases and optimizations.</p>
 
 <table class="ompstatus">
 <thead>
-  <tr class="separator">
+  <tr>
     <th>Feature</th>
     <th>GCC Version</th>
     <th>Comments</th>
@@ -492,7 +492,7 @@ than listed, depending on resolved corner cases and optimizations.</p>
 
 <table class="ompstatus">
 <thead>
-  <tr class="separator">
+  <tr>
     <th>Feature</th>
     <th>GCC Version</th>
     <th>Comments</th>
@@ -732,7 +732,7 @@ than listed, depending on resolved corner cases and optimizations.</p>
 
 <table class="ompstatus">
 <thead>
-  <tr class="separator">
+  <tr>
     <th>Feature</th>
     <th>GCC Version</th>
     <th>Comments</th>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc.css                  | 6 +++---
 htdocs/projects/gomp/index.html | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2022-05-17  9:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220517094803.68BDE3858D3C@sourceware.org \
    --to=burnus@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).