From: James Prestwood <prestwoj at gmail.com>
To: ell at lists.01.org
Subject: [ANNOUNCE] ELL switching to new mailing list
Date: Wed, 15 Jun 2022 16:52:21 -0700 [thread overview]
Message-ID: <5f4906917eee2844614fba727965050c19cf757f.camel@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
Hello All,
ELL is swiching to a new mailing list: ell(a)lists.linux.dev. This list
is currently active and ready so any future patches, questions, or
comments can be sent there!
You might be wondering, why is this being done? The reason for this
change is to enable an automated CI for ELL to catch regressions, build
breaks, or any other issues which previously required manual testing.
You will see the CI results from you're changes in patchwork:
https://patchwork.kernel.org/project/ell/list/
Note the CI is still in a trial stage, so email notifications have been
disabled. You will not receive any notifications about test results but
know that maintainers are checking the results and will point you to
any problems that are found.
If you have any questions please don't hesitate to ask.
Thanks,
James
reply other threads:[~2022-06-15 23:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5f4906917eee2844614fba727965050c19cf757f.camel@gmail.com \
--to=ell@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).