From: tpeplt <tpeplt@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Missing GNU mailing lists?
Date: Thu, 31 Aug 2023 16:48:04 -0400 [thread overview]
Message-ID: <87o7inc517.fsf@gmail.com> (raw)
In-Reply-To: <83bkeng6l4.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 31 Aug 2023 07:48:39 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>>
>
> I hope you wrote to mailman@gnu.org about that as well. We don't
> manage the GNU mailing lists here, so we cannot fix any problems with
> them.
Yes, I did as you had suggested. I later received a reply saying that
it was a significant problem and that they would be working to fix it.
Today, another reply said that it had been fixed. I checked the link
with ‘eww’ to confirm that it has been. The link now produces a table
with approximately 800 mailing list entries.
--
next prev parent reply other threads:[~2023-08-31 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 19:19 Missing GNU mailing lists? tpeplt
2023-08-30 19:27 ` Eli Zaretskii
2023-08-30 19:40 ` tpeplt
2023-08-30 20:12 ` Juergen Fenn
2023-08-31 4:48 ` Eli Zaretskii
2023-08-31 20:48 ` tpeplt [this message]
2023-09-01 5:34 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7inc517.fsf@gmail.com \
--to=tpeplt@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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).