From: Jonny Grant <jg@jguk.org>
To: fche@elastic.org, overseers@sourceware.org
Subject: Re: sourceware.org 404 link
Date: Sat, 08 Dec 2018 07:53:00 -0000 [thread overview]
Message-ID: <CAGNDjJvmRT3C2-XQ0okoTQp_DRGYkFQoHoUdtw5Zpd8wHYVGaw@mail.gmail.com> (raw)
In-Reply-To: <CAGNDjJviYRBiTr4DOt+1=2_f9ang1J5cDRqrzVaYLLaZhAoD+Q@mail.gmail.com>
BTW, overseers@elastic.org is bouncing
I think you meant overseers@sourceware.org
On Sat, 8 Dec 2018 at 07:51, Jonny Grant <jg@jguk.org> wrote:
>
> Many thanks Frank
> Yes, if there is a validator, would be good to run.
>
> On Sat, 1 Dec 2018 at 20:04, Frank Ch. Eigler <fche@elastic.org> wrote:
> >
> > Hi, Jonny -
> >
> > > Would you consider running the W3C link checker regularly on sourceware.org?
> > > https://validator.w3.org/checklink
> >
> > Not a bad idea.
> >
> > > This page has a broken Tutorial html link
> > > [...]
> > > https://sourceware.org/systemtap/tutorial/
> > > https://sourceware.org/systemtap/langref/
> >
> > These pages have been regenerated, thanks.
> >
> > > Line: 20http://sourceware.org/systemtap/wiki
> > > *Status*: 403 FORBIDDEN
> >
> > ... except that this is a false positive. That particular validator
> > program probably hit sourceware's overload self-protection mechanisms.
> > We could probably run our own validator locally.
> >
> >
> > - FChE
prev parent reply other threads:[~2018-12-08 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 21:02 Jonny Grant
[not found] ` <20181201200425.GA128408@elastic.org>
[not found] ` <CAGNDjJviYRBiTr4DOt+1=2_f9ang1J5cDRqrzVaYLLaZhAoD+Q@mail.gmail.com>
2018-12-08 7:53 ` Jonny Grant [this message]
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=CAGNDjJvmRT3C2-XQ0okoTQp_DRGYkFQoHoUdtw5Zpd8wHYVGaw@mail.gmail.com \
--to=jg@jguk.org \
--cc=fche@elastic.org \
--cc=overseers@sourceware.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).