From: Mark Wielaard <mark@klomp.org>
To: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>,
"classpath@gnu.org" <classpath@gnu.org>
Cc: "Andrew Hughes" <gnu.andrew@redhat.com>,
Andïï <gnu_andrew@member.fsf.org>,
Andïï <gnu.andrew.rocks@gmail.com>,
"Andrew Haley" <aph@redhat.com>,
java@gcc.gnu.org, "Mario Torre" <neugens@redhat.com>
Subject: Re: Status of GNU Classpath
Date: Tue, 07 Feb 2023 11:47:03 +0100 [thread overview]
Message-ID: <0469b68a9f7626380cb9e4676abe5af20aff892a.camel@klomp.org> (raw)
In-Reply-To: <CABDcavbPMXbZHXaXkEvPUEqwMwkcJ7kpA9D1uXVB3i7OE9g4sQ@mail.gmail.com>
Hi Guillermo,
On Mon, 2023-02-06 at 13:55 +0100, Guillermo Rodriguez Garcia wrote:
> Summary: It does not seem to be possible to join the mailing list
> anymore. Additionally, emails sent to the list are not being delivered
> to subscribers, nor included in the archives (see details in the email
> below).
Urgh. Sorry. I did see your earlier email, but then Fosdem happened and
I forgot. So at one point classpath got so much email that
lists.gnu.org couldn't handle it in time. So we arranged to handle all
emails on developer.classpath.org. But at some point that machine had
to be migrated and the mailinglist archives haven't been put back.
There are backups and I'll contact the fsf-tech team to see if they can
incorporate those archives and handle the mailinglist directly again.
Cheers,
Mark
next prev parent reply other threads:[~2023-02-07 10:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABDcavY1sfVXs=zhF3fB+LS+HbszaDzs4KUzbkryFyz13ngtwQ@mail.gmail.com>
2023-02-06 12:55 ` Guillermo Rodriguez Garcia
2023-02-06 14:25 ` Ricardo Wurmus
2023-02-06 16:16 ` Guillermo Rodriguez Garcia
2023-02-08 10:42 ` Ricardo Wurmus
2023-02-08 15:55 ` Guillermo Rodriguez Garcia
2023-02-10 19:08 ` Ricardo Wurmus
2023-02-07 10:34 ` Andrew Haley
2023-02-07 10:55 ` Mark Wielaard
2023-02-07 10:47 ` Mark Wielaard [this message]
2023-02-07 13:00 ` Guillermo Rodriguez Garcia
2023-09-13 10:06 ` Guillermo Rodriguez Garcia
2023-09-14 8:15 ` Mark Wielaard
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=0469b68a9f7626380cb9e4676abe5af20aff892a.camel@klomp.org \
--to=mark@klomp.org \
--cc=aph@redhat.com \
--cc=classpath@gnu.org \
--cc=gnu.andrew.rocks@gmail.com \
--cc=gnu.andrew@redhat.com \
--cc=gnu_andrew@member.fsf.org \
--cc=guille.rodriguez@gmail.com \
--cc=java@gcc.gnu.org \
--cc=neugens@redhat.com \
/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).