public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [wwwdocs, patch] OpenMP update for gcc-13/changes.html + projects/gomp/
Date: Fri, 24 Feb 2023 02:02:32 +0100 (CET)	[thread overview]
Message-ID: <a8cb1eb3-7444-226f-fff7-d33899dc380b@pfeifer.com> (raw)
In-Reply-To: <34b4c8eb-83a3-1a5a-f774-0076e2e8f580@codesourcery.com>

On Thu, 23 Feb 2023, Tobias Burnus wrote:
> PS: I also removed a stray </code>, but admittedly only after the
> commit. I found it by manually running those through the w3 validator
> site. However, I did not see an automatic email, either it takes longer
> or does it no longer run? It did in the past!

You are right, and this is a sore / sad point: validator.w3.org that we
used in the past now only supports interactive sessions. And they even
broke support for the Referer header, so I also had to remove the checking 
link I had embedded in all of our pages.

These days I invoke the validator (via a version of the original script) 
when I see a commit. Which indeed leads to many orders of magnitude longer 
delays.

Sadly I don't have a better alternative. :-(

Gerald

  reply	other threads:[~2023-02-24  1:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 10:59 Tobias Burnus
2023-02-22 23:29 ` Gerald Pfeifer
2023-02-23 14:50   ` Tobias Burnus
2023-02-24  1:02     ` Gerald Pfeifer [this message]
2023-02-24  7:32       ` Benson Muite
2023-02-24 11:10         ` Benson Muite

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=a8cb1eb3-7444-226f-fff7-d33899dc380b@pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=tobias@codesourcery.com \
    /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).