All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Linux OpenRISC <linux-openrisc@vger.kernel.org>
Subject: OpenRISC mailing list moves from librecores.org to vger.kernel.org
Date: Wed, 1 Feb 2023 00:23:56 +0900	[thread overview]
Message-ID: <Y9kyjEaTtPQ5sKeH@antec> (raw)

Hi All,

After some recent issues in infrastructure the mailing lists at librecores.org
have been shut down.  This was brought to my attention earlier this week and we
have migrated all users over to to a new mailing list hosted on the
vger.kernel.org infrastructure.

This is good news as it should provide a very solid mailing list for our future
OpenRISC discussions.

Sorry, I don't have too much more information on whyy the librecores.org
infrastructure went down.  But it does seem to follow the announced shutdown of
librecores[1].

If you want to manage your subscription please do that via vger.kernel.org[2].

Next steps:
 - I have requested to get archiving setup on lore.kernel.org
 - I will be sending out a kernel patch to move the OpenRISC risk development
   patches over to this new list.
 - Need to update the OpenRISC website.
 - Update any other projects linking to the old list.

Thank You,

-Stafford

[1] https://www.fossi-foundation.org/2022/10/19/librecores
[2] http://vger.kernel.org/vger-lists.html#linux-openrisc

             reply	other threads:[~2023-01-31 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 15:23 Stafford Horne [this message]
2023-01-31 15:35 ` OpenRISC mailing list moves from librecores.org to vger.kernel.org Geert Uytterhoeven
2023-01-31 15:42   ` Stafford Horne
2023-01-31 15:51     ` Geert Uytterhoeven
2023-02-19 20:59       ` Geert Uytterhoeven
2023-01-31 16:01 ` Vad Rulezz
2023-02-04 10:20 ` Stafford Horne

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=Y9kyjEaTtPQ5sKeH@antec \
    --to=shorne@gmail.com \
    --cc=linux-openrisc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.