From: Christopher Faylor <cgf-use-the-mailinglist-please@gnu.org>
To: overseers@sourceware.org
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
"gcc mailing list" <gcc@gcc.gnu.org>,
"Thomas König" <tk@tkoenig.net>
Subject: Re: gcc mailing list is not being archived
Date: Mon, 9 Mar 2020 15:47:55 -0400 [thread overview]
Message-ID: <20200309194755.GC6843@cgf.cx> (raw)
In-Reply-To: <20200309141031.GB67879@elastic.org>
On Mon, Mar 09, 2020 at 10:10:31AM -0400, Frank Ch. Eigler via Overseers wrote:
>Hi -
>
>> one more point: The gcc mailing list including this discussion is
>> currently not being archived, the last message is from 2020-03-06.
>
>Found & fixed a permission problem with the mailmnan archives.
>Let's see if this one makes it in now.
I'll repopulate the archive with the missing messages when I have the
chance.
cgf
prev parent reply other threads:[~2020-03-09 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 13:59 Thomas König
2020-03-09 14:10 ` Frank Ch. Eigler
2020-03-09 19:47 ` Christopher Faylor [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=20200309194755.GC6843@cgf.cx \
--to=cgf-use-the-mailinglist-please@gnu.org \
--cc=fche@elastic.org \
--cc=gcc@gcc.gnu.org \
--cc=overseers@sourceware.org \
--cc=tk@tkoenig.net \
/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).