From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@palves.net>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
gdb@sourceware.org, Jonny Grant <jg@jguk.org>
Subject: Re: http://mail.gnu.org/mailman/listinfo/bug-gdb/ down
Date: Mon, 29 Jun 2020 10:48:17 -0700 [thread overview]
Message-ID: <20200629174817.GB28752@adacore.com> (raw)
In-Reply-To: <ac9fdfa2-0bc7-4e39-dae8-b03251019afc@palves.net>
> Wasn't bug-gdb@gnu.org converted to a gdb@sourceware.org alias years ago?
>
> https://sourceware.org/legacy-ml/gdb/2014-11/msg00023.html
>
> Here,
>
> https://sourceware.org/legacy-ml/gdb/2014-12/msg00001.html
>
> Sergio said:
>
> "The GNU sysadmins told me that both lists now redirect here. I hope it works OK."
>
>
> I'm surprised the archives even exist beyond 2014.
>
> For example, here:
>
> https://lists.gnu.org/archive/html/bug-gdb/2016-01/threads.html
>
> we see an email:
>
> https://lists.gnu.org/archive/html/bug-gdb/2016-01/msg00000.html
>
> that I can't find on the gdb@sourceware.org archive:
>
> https://sourceware.org/legacy-ml/gdb/2016-01/
>
> Did the redirect stop working or something?
I just did an experiment, and sent an email to bug-gdb, and got
an email back from gdb-owner that it is being held in quarantine
waiting for and admin to approve it. So I think the redirection
is working, but now the mailing-list settings don't let those through
without moderator approval.
I was wondering how active the newsgroup might be. One can take
a look there:
https://groups.google.com/forum/#!forum/gnu.gdb.bug
To sumarize:
- One post in 2019, with a question and no replies;
- Nothing in 2018;
- A stream of spam in 2017;
- Two posts in 2016, with no answers;
- Nothing in 2015;
- More activity in 2014.
I'm wondering if we shouldn't just ask gnu.org to shut gnu.gdb.bug down.
Then we can adapt the mailinglist page on the GDB website accordingly,
with a link to the old archives for reference (as long as they are live).
--
Joel
next prev parent reply other threads:[~2020-06-29 17:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 11:07 Jonny Grant
2020-05-26 14:17 ` Simon Marchi
2020-05-27 22:12 ` Jonny Grant
2020-05-27 22:26 ` Jonny Grant
2020-05-28 6:47 ` Eli Zaretskii
2020-05-30 0:20 ` Jonny Grant
2020-05-30 6:19 ` Eli Zaretskii
2020-06-27 19:37 ` Jonny Grant
2020-06-28 1:27 ` Joel Brobecker
2020-06-28 5:20 ` Andreas Schwab
2020-06-28 15:26 ` Jonny Grant
2020-06-28 15:36 ` Joel Brobecker
2020-06-29 11:44 ` Pedro Alves
2020-06-29 17:48 ` Joel Brobecker [this message]
2020-07-06 18:54 ` Joel Brobecker
2020-07-08 22:03 ` Jonny Grant
2020-06-28 15:21 ` Jonny Grant
2020-05-28 6:31 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200629174817.GB28752@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=jg@jguk.org \
--cc=pedro@palves.net \
--cc=schwab@linux-m68k.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).