From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Olivier Hainque <hainque@adacore.com>
Cc: GCC Development <gcc@gcc.gnu.org>,
Overseers mailing list <overseers@sourceware.org>
Subject: Re: blacklisted after announce on GNU cauldron ?
Date: Thu, 23 Apr 2020 11:45:09 -0400 [thread overview]
Message-ID: <20200423154509.GB6934@cgf.cx> (raw)
In-Reply-To: <FFC95A3B-BB8B-4D9C-A696-07319B4FE3BD@adacore.com>
On Thu, Apr 23, 2020 at 05:13:13PM +0200, Olivier Hainque wrote:
>Hi Frank,
>
>> On 23 Apr 2020, at 16:34, Frank Ch. Eigler <fche@elastic.org> wrote:
>>
>> Hi -
>>
>>>> A re-subscription attempt to the gcc mailing list just
>>>> failed, expectedly I guess.
>>
>> I see no sign in the logs of Olivier being banned in any form. Please
>> resubscribe online and forward complete failure symptoms if you
>> believe this is still happening.
>
>Thanks for your feedback!
>
>I managed to subscribe again by going through the gcc
>list specific info page :-)
>
>My previous attempts were issued from
>
> https://gcc.gnu.org/lists.html#subscribe
>
>Subscribing from there doesn't work and leads
>to a page which provides instructions which don't work
>either.
>
From there I thought the coincidence was troubling.
>
>There is actually a FAQ link on the instructions page,
>which I just checked, and ... it directs to a 404 page:
>
> https://sourceware.org/pipermail/index.html#faqs
>
>I'll try to re-subscribe to gcc-patches now.
All of the above is handled by whomever is responsible for the
gcc web pages. It would be nice if someone fixed those links.
next prev parent reply other threads:[~2020-04-23 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3CDC7322-A1AE-4045-AC3C-72924DF23064@adacore.com>
2020-04-23 10:11 ` Richard Earnshaw
2020-04-23 14:34 ` Frank Ch. Eigler
2020-04-23 15:13 ` Olivier Hainque
2020-04-23 15:45 ` Christopher Faylor [this message]
[not found] ` <CAH6eHdSBsVL0its+nDYpQ8ySJEHLbKR1j2VVbak9B4_yUqcvLQ@mail.gmail.com>
[not found] ` <CAH6eHdRxmsUK7W0Y6ZC-+v92FH9AP-sNRjE5zfp4t1Pi+VVg7Q@mail.gmail.com>
2020-04-23 18:39 ` Christopher Faylor
2020-04-23 15:00 ` Christopher Faylor
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=20200423154509.GB6934@cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=hainque@adacore.com \
--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).