From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: [ANNOUNCE] NVDIMM development move to nvdimm@lists.linux.dev
Date: Tue, 20 Apr 2021 13:34:00 -0700 [thread overview]
Message-ID: <CAPcyv4jyD57mTifvU5yCd6N3-pceyCC0=A83JovXuMR8=zVewQ@mail.gmail.com> (raw)
There have been multiple occasions recently where people reported
trouble managing their subscription to linux-nvdimm@lists.01.org. The
spam filtering also appears less robust compared to other Linux
development lists.
There are also side benefits to being on kernel.org infrastructure as
it has a direct path to inject messages into the public-inbox
repository on lore, and feed the patchwork-bot.
You can find the subscription link here:
https://subspace.kernel.org/lists.linux.dev.html
For the v5.13 merge window I'll submit a patch to switch the list from
linux-nvdimm@lists.01.org to nvdimm@lists.linux.dev, and plan to
shutdown linux-nvdimm@ a couple months later around the v5.14 merge
window.
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
reply other threads:[~2021-04-20 20:34 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='CAPcyv4jyD57mTifvU5yCd6N3-pceyCC0=A83JovXuMR8=zVewQ@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=linux-nvdimm@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.