public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@elastic.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org,
	"Joseph S. Myers" <joseph@codesourcery.com>,
	Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: No more notifications of wwwdocs commits?
Date: Sun, 8 Mar 2020 18:30:44 -0400	[thread overview]
Message-ID: <20200308223040.GA94530@elastic.org> (raw)
In-Reply-To: <alpine.LSU.2.21.2003082257380.4184@anthias.pfeifer.com>

Hi -

> There definitely are several things not working properly as far as
> our web page infrastructure goes:
> 
> - https://gcc.gnu.org/pipermail/gcc-cvs-wwwdocs/2020/date.html
>   misses the last two commits:
> 
> commit 09a7a9579b59619ea3f601b821ec8b9dd3fe708e (HEAD -> master, 
> commit 8a562ce34e441587b87d5e5bc2ebb58f4ce630b9

OK, will look into it, though the git-email processing is done
by the adacore hooks AIUI.

> - gcc.gnu.org/spam.html misses the last commit.
> 
> Just to make sure, from here gcc.gnu.org has address 8.43.85.97 and
> the system reports an uptime of 158 days (which seems a bit fishy)?

That is correct - it is fantastic fish.

- FChE

  reply	other threads:[~2020-03-08 22:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-07 23:41 Gerald Pfeifer
2020-03-08 17:42 ` Christopher Faylor
2020-03-08 22:04   ` Gerald Pfeifer
2020-03-08 22:30     ` Frank Ch. Eigler [this message]
2020-03-09 14:05       ` Joseph Myers
2020-03-09 17:59         ` Christopher Faylor
2020-03-09 21:02           ` Joseph Myers
2020-03-09  3:33 ` Frank Ch. Eigler
2020-03-09 12:18   ` gcc.gnu.org web site updates broken (was: No more notifications of wwwdocs commits?) Gerald Pfeifer
2020-03-09 14:14     ` Frank Ch. Eigler

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=20200308223040.GA94530@elastic.org \
    --to=fche@elastic.org \
    --cc=gerald@pfeifer.com \
    --cc=joseph@codesourcery.com \
    --cc=overseers@gcc.gnu.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).