From: "Frank Ch. Eigler" <fche@elastic.org>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: overseers@gcc.gnu.org
Subject: Re: No more notifications of wwwdocs commits?
Date: Sun, 8 Mar 2020 23:33:11 -0400 [thread overview]
Message-ID: <20200309033311.GE94530@elastic.org> (raw)
In-Reply-To: <alpine.LSU.2.21.2003080037400.4184@anthias.pfeifer.com>
Hi -
> The regular mailing lists appear to work after the migration, and
> you folks probably are still hacking on things right now, so I just
> wanted to note that notifications for wwwdocs commits (via the
> gcc-cvs-wwwdocs list) do not appear to be happening right now.
The metahtml program needed to be lovingly fetched, built, and lightly
installed, and some git sharedrepository flags fixed; now at least one
can commit to gcc-wwwdocs.git and have it propagate. I don't know if
that also fixes the notification emails tho.
- FChE
next prev parent reply other threads:[~2020-03-09 3:33 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
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 [this message]
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=20200309033311.GE94530@elastic.org \
--to=fche@elastic.org \
--cc=gerald@pfeifer.com \
--cc=overseers@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).