From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] Add openrisc@lists.librecores.org to lore.kernel.org
Date: Fri, 29 Apr 2022 12:14:40 +0900 [thread overview]
Message-ID: <CAAfxs75mxjefcTi5ficG0YvDr1THkPGG6aOxX0oor6WWTUngxA@mail.gmail.com> (raw)
In-Reply-To: <20220428201950.6emdw5i2fvyktt2i@nitro.local>
+cc Stefan and Philpp,
On Fri, Apr 29, 2022, 5:19 AM Konstantin Ryabitsev <
konstantin@linuxfoundation.org> wrote:
> On Thu, Apr 28, 2022 at 01:15:09PM +0200, Jason A. Donenfeld wrote:
> > Hi folks,
> >
> > Any interest in getting this mailing list up on lore.kernel.org? This
> > would make sense since it's the mailing list specified in the Linux
> > MAINTAINERS file for OpenRISC development. It'd require the list
> > administrator to send the current list archives to Konstantin and then
> > add some archiver as a subscriber. Given this is a fairly normal
> > mailman list, that doesn't seem too hard.
>
> We can add it, but it would be great if the list can be made DKIM-compliant
> first:
>
> 1. turn off subject modification, if possible
> 2. remove body modification, if present (mailman list footers, etc)
>
> This way any messages sent to this list and to any other lists are properly
> deduplicated.
>
I think it's a good idea, I am not an admin at librecores. Can you guys
help out?
-stafford
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20220429/a002d911/attachment.htm>
next prev parent reply other threads:[~2022-04-29 3:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 11:15 [OpenRISC] Add openrisc@lists.librecores.org to lore.kernel.org Jason A. Donenfeld
2022-04-28 20:19 ` Konstantin Ryabitsev
2022-04-29 3:14 ` Stafford Horne [this message]
2022-05-03 16:38 ` Philipp Wagner
2022-05-11 16:55 ` Konstantin Ryabitsev
2022-05-11 20:53 ` 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=CAAfxs75mxjefcTi5ficG0YvDr1THkPGG6aOxX0oor6WWTUngxA@mail.gmail.com \
--to=shorne@gmail.com \
--cc=openrisc@lists.librecores.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 NNTP newsgroup(s).