From: "Arnd Bergmann" <arnd@arndb.de>
To: "Wallentowitz, Stefan" <stefan.wallentowitz@hm.edu>,
"Stafford Horne" <shorne@gmail.com>
Cc: Jonas Bonn <jonas@southpole.se>,
postmaster@vger.kernel.org,
"openrisc@lists.librecores.org" <openrisc@lists.librecores.org>,
"mail@philipp-wagner.com" <mail@philipp-wagner.com>,
"info@fossi-foundation.org" <info@fossi-foundation.org>
Subject: Re: OpenRISC mailing list on lists.librecores.org status?
Date: Fri, 27 Jan 2023 21:59:00 +0100 [thread overview]
Message-ID: <72309fb9-f747-4e6a-a8a0-0843a95c9793@app.fastmail.com> (raw)
In-Reply-To: <22EED3FC-CB23-4245-B490-02D095CD7ABB@hm.edu>
On Fri, Jan 27, 2023, at 21:17, Wallentowitz, Stefan wrote:
>> Am 27.01.2023 um 21:12 schrieb Stafford Horne <shorne@gmail.com>:
>> On Fri, Jan 27, 2023 at 08:51:13AM +0100, Arnd Bergmann wrote:
>>> I got a bounce from a discussion[1] of a kernel patch, with status
>>> "lists.librecores.org[88.198.125.70]:25: No route to host". Is that
>>> a temporary problem, or does this list have to move after the
>>> librecores.org domain now redirects to fossi-foundation.org [2]?
>>
>> I didnt't realize this, I have moved to London in the last few months and
>> haven't been doing a lot of OpenRISC work while I get settled so this slipped
>> past my radar.
>>
>> CCing Stefan and Philipp who managed the mailing list. It seems the last mail I
>> received for the mailing list was 8 days ago.
>>
>> Philipp is there a new mailing list server/domain now? What has happened to the
>> archive of openrisc mailing list?
>
> Sorry, we have outages at the moment and have started to mitigate by
> looking for alternatives.
>
> Arnd, do you have a suggestion for a mailman service for an
> architecture’s kernel mailing list? Sorry for the inconvenience, I will
> look into keeping the service stable. Is Google groups an acceptable
> target for this mailing list?
I would recommend hosting on vger.kernel.org, which has a lot of other
architectures already.
Adding postmaster@vger.kernel.org to Cc, they can probably help you.
Arnd
next parent reply other threads:[~2023-01-28 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6aa3b785-5ea2-41d4-ad16-56c5b179cbe8@app.fastmail.com>
[not found] ` <Y9QwJIwmRF3wmbGR@antec>
[not found] ` <22EED3FC-CB23-4245-B490-02D095CD7ABB@hm.edu>
2023-01-27 20:59 ` Arnd Bergmann [this message]
[not found] ` <1a601f5d-1a3c-59eb-02f4-fa10b5664f09@eaglescrag.net>
[not found] ` <520C5853-52C8-4305-A866-FEE73695AE67@hm.edu>
[not found] ` <bf4efc4f-ab46-6379-805f-923051832b11@eaglescrag.net>
2023-01-27 21:58 ` OpenRISC mailing list on lists.librecores.org status? Arnd Bergmann
[not found] ` <ea758038-6f2b-3931-8fde-c973e20943b6@eaglescrag.net>
[not found] ` <Y9TV8DRbVmivrTWi@antec>
[not found] ` <55ad7182-5128-68e4-b685-e4dd743e6d71@eaglescrag.net>
[not found] ` <Y9W3Bit1LR/KQMsG@antec>
2023-01-29 17:12 ` Philipp Wagner
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=72309fb9-f747-4e6a-a8a0-0843a95c9793@app.fastmail.com \
--to=arnd@arndb.de \
--cc=info@fossi-foundation.org \
--cc=jonas@southpole.se \
--cc=mail@philipp-wagner.com \
--cc=openrisc@lists.librecores.org \
--cc=postmaster@vger.kernel.org \
--cc=shorne@gmail.com \
--cc=stefan.wallentowitz@hm.edu \
/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).