From: Stafford Horne <shorne@gmail.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Openrisc <openrisc@lists.librecores.org>,
Stefan Wallentowitz <stefan.wallentowitz@gmail.com>,
Philipp Wagner <mail@philipp-wagner.com>
Subject: Re: [OpenRISC] Add openrisc@lists.librecores.org to lore.kernel.org
Date: Thu, 12 May 2022 05:53:36 +0900 [thread overview]
Message-ID: <YnwiUOt7biixqPaZ@antec> (raw)
In-Reply-To: <CAMwyc-QRwkSa4rEDRsqiHT+cYPACrHm4N6N5xUNXuqJwi6yVVg@mail.gmail.com>
On Wed, May 11, 2022 at 12:55:05PM -0400, Konstantin Ryabitsev wrote:
> On Tue, 3 May 2022 at 12:38, Philipp Wagner <mail@philipp-wagner.com> wrote:
> > > 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
> >
> > done (unset the subject_prefix setting)
> >
> > > 2. remove body modification, if present (mailman list footers, etc)
> >
> > Done that as well (cleared msg_footer setting).
> >
> > > 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?
> >
> > I made the changes above, let me know if that's not sufficient and more
> > changes are needed.
>
> Looks good. The list is now archived here:
> https://lore.kernel.org/openrisc/
Thanks it looks good. I have added a link to this here:
https://openrisc.io/community
-Stafford
prev parent reply other threads:[~2022-05-11 20:53 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
2022-05-03 16:38 ` Philipp Wagner
2022-05-11 16:55 ` Konstantin Ryabitsev
2022-05-11 20:53 ` Stafford Horne [this message]
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=YnwiUOt7biixqPaZ@antec \
--to=shorne@gmail.com \
--cc=Jason@zx2c4.com \
--cc=konstantin@linuxfoundation.org \
--cc=mail@philipp-wagner.com \
--cc=openrisc@lists.librecores.org \
--cc=stefan.wallentowitz@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