public inbox for openrisc@lists.librecores.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux OpenRISC <linux-openrisc@vger.kernel.org>
Subject: Re: OpenRISC mailing list moves from librecores.org to vger.kernel.org
Date: Wed, 1 Feb 2023 00:42:06 +0900	[thread overview]
Message-ID: <Y9k2zjTd246QCDVO@antec> (raw)
In-Reply-To: <CAMuHMdXiV92J538Yq-yFi0b25u2GSEoR6XAW5t=kR2dR3dEXDg@mail.gmail.com>

On Tue, Jan 31, 2023 at 04:35:30PM +0100, Geert Uytterhoeven wrote:
> 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

We do have most/all of the librecores.org history archived to lore already[1].

[1] https://lore.kernel.org/openrisc/

> 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 ;-)

I don't have that old history and would love to have it up on lore if possible.
Let me CC you on my other mail to see what we can do.

Thank you,

-Stafford


  reply	other threads:[~2023-01-31 15:42 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
2023-01-31 15:42   ` Stafford Horne [this message]
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=Y9k2zjTd246QCDVO@antec \
    --to=shorne@gmail.com \
    --cc=geert@linux-m68k.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox