From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stafford Horne <shorne@gmail.com>
Cc: Linux OpenRISC <linux-openrisc@vger.kernel.org>
Subject: Re: OpenRISC mailing list moves from librecores.org to vger.kernel.org
Date: Tue, 31 Jan 2023 16:35:30 +0100 [thread overview]
Message-ID: <CAMuHMdXiV92J538Yq-yFi0b25u2GSEoR6XAW5t=kR2dR3dEXDg@mail.gmail.com> (raw)
In-Reply-To: <Y9kyjEaTtPQ5sKeH@antec>
Hi Stafford,
On Tue, Jan 31, 2023 at 4:25 PM Stafford Horne <shorne@gmail.com> wrote:
> 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.
Thanks for taking care of this!
> Next steps:
> - I have requested to get archiving setup on lore.kernel.org
Do you have a good archive of the old mailing list to populate lore,
or do you need help to fill in some gaps?
My local archive goes back to November 25th, 2013.
Oh, it was called linux@lists.openrisc.net those days ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2023-01-31 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 15:23 OpenRISC mailing list moves from librecores.org to vger.kernel.org Stafford Horne
2023-01-31 15:35 ` Geert Uytterhoeven [this message]
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='CAMuHMdXiV92J538Yq-yFi0b25u2GSEoR6XAW5t=kR2dR3dEXDg@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=shorne@gmail.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 NNTP newsgroup(s).